{"id":29266,"date":"2015-02-16T14:44:08","date_gmt":"2015-02-16T19:44:08","guid":{"rendered":"http:\/\/www.opensource.im\/uncategorized\/cryptography-to-prevent-satellite-collisions.php"},"modified":"2015-02-16T14:44:08","modified_gmt":"2015-02-16T19:44:08","slug":"cryptography-to-prevent-satellite-collisions","status":"publish","type":"post","link":"https:\/\/euvolution.com\/open-source-convergence\/cryptography\/cryptography-to-prevent-satellite-collisions.php","title":{"rendered":"Cryptography to prevent satellite collisions"},"content":{"rendered":"<p><p>    Chuck Bednar for redOrbit.com  Your Universe    Online  <\/p>\n<p>    Cryptography, the practice and study of techniques for secure    communication in the presence of third parties, could help    prevent collisions among the thousands of commercial and spy    satellites currently in orbit around the Earth. It would also    maintain privacy, according to experts.  <\/p>\n<p>    In an article written last month for Scientific    American, Brett Hemenway, a research assistant    professor with the University of Pennsylvania who focuses on    cryptography, and William Welser IV, a space policy expert,    explain how it can help avoid potential satellite collisions.  <\/p>\n<p>    One such collision took place in February 2009, the authors    explained, when the US Iridium 33 satellite and the Russian    Cosmos 2251 collided and were both destroyed. Telescopes    tracking the two probes from the ground indicated that they    should have missed one another, but data from instruments on    board either of them would have revealed that they were on a    collision course.  <\/p>\n<p>    That information was not used, however, because it was deemed    to be top-secret.  <\/p>\n<p>    Satellite owners view the locations and trajectories of their    on-orbit assets as private, Welser and Hemenway wrote.    Companies fear that sharing the exact positions of their    satellites could help the competition determine the full extent    of their capabilities, while governments are afraid that    revealing such information could compromise their national    security, they explained.  <\/p>\n<p>    Yet even minor collisions could cause millions of dollars worth    of damage. Debris can be knocked into the path of other    satellites, spacecraft carrying a human crew, or even the    International Space Station (ISS), the authors wrote. The 2009    incident served as a warning to officials to find a way to fix    the problem, but without revealing too much information.  <\/p>\n<p>    Adding a third party  <\/p>\n<p>    In the current working solution, the worlds four largest    satellite communications providers have teamed up with a    trusted third party: Analytical Graphics. The company    aggregates their orbital data and alerts participants when    satellites are at risk, wrote Hemenway and Welser, adding that    the arrangement requires that all participants maintain mutual    trust of the third party.  <\/p>\n<p>    Analytical Graphics, also known as AGI, makes commercial    modeling and analysis software for the aerospace, defense, and    intelligence communities. The company was founded in 1989 and    is headquartered in Exton, Pennsylvania, though it also has    offices located in Colorado, California, Washington DC, the UK,    and Singapore. Its current CEO is Paul Graziani.  <\/p>\n<p><!-- Auto Generated --><\/p>\n<p>Read the original post:<br \/>\n<a target=\"_blank\" href=\"http:\/\/www.redorbit.com\/news\/space\/1113334629\/cryptography-to-prevent-satellite-collisions\" title=\"Cryptography to prevent satellite collisions\">Cryptography to prevent satellite collisions<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p> Chuck Bednar for redOrbit.com Your Universe Online Cryptography, the practice and study of techniques for secure communication in the presence of third parties, could help prevent collisions among the thousands of commercial and spy satellites currently in orbit around the Earth. It would also maintain privacy, according to experts. <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1600],"tags":[],"class_list":["post-29266","post","type-post","status-publish","format-standard","hentry","category-cryptography"],"_links":{"self":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts\/29266"}],"collection":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/comments?post=29266"}],"version-history":[{"count":0,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts\/29266\/revisions"}],"wp:attachment":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/media?parent=29266"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/categories?post=29266"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/tags?post=29266"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}