<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' xmlns:georss='http://www.georss.org/georss' xmlns:gd='http://schemas.google.com/g/2005' xmlns:thr='http://purl.org/syndication/thread/1.0'><id>tag:blogger.com,1999:blog-159147093590377321</id><updated>2011-11-28T05:07:38.154+05:00</updated><category term='hack'/><category term='overview of gsm'/><category term='GSM'/><category term='logical channel'/><category term='A8'/><category term='Kc'/><category term='physical channel'/><category term='best'/><category term='authentication'/><category term='camera'/><category term='security'/><category term='A3'/><category term='privacy'/><category term='3G'/><category term='A5/3'/><category term='channels'/><category term='encryption'/><category term='GSM books'/><category term='A5/1'/><category term='KASUMI'/><category term='control channel'/><category term='Ki'/><category term='A5/2'/><category term='gsm systems'/><category term='axis'/><category term='SRES'/><title type='text'>GSM Security</title><subtitle type='html'>The blog is created to inform and share the knowledge regarding the GSM security issues.</subtitle><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://gsmsecurity.blogspot.com/feeds/posts/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/159147093590377321/posts/default?max-results=100'/><link rel='alternate' type='text/html' href='http://gsmsecurity.blogspot.com/'/><link rel='hub' href='http://pubsubhubbub.appspot.com/'/><author><name>Imran Aziz</name><uri>http://www.blogger.com/profile/16311802287455383093</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>10</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>100</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-159147093590377321.post-6301407288575745552</id><published>2009-05-23T14:00:00.003+06:00</published><updated>2009-05-23T14:17:05.813+06:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='best'/><category scheme='http://www.blogger.com/atom/ns#' term='overview of gsm'/><category scheme='http://www.blogger.com/atom/ns#' term='GSM books'/><category scheme='http://www.blogger.com/atom/ns#' term='GSM'/><category scheme='http://www.blogger.com/atom/ns#' term='gsm systems'/><title type='text'>Best Free GSM Books</title><content type='html'>Get the best free GSM books and share with the others. You can find the one of your interest on following links:&lt;br /&gt;&lt;br /&gt;Will be available shortly.&lt;br /&gt;&lt;br /&gt;Thanks&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/159147093590377321-6301407288575745552?l=gsmsecurity.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://gsmsecurity.blogspot.com/feeds/6301407288575745552/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://gsmsecurity.blogspot.com/2009/05/best-free-gsm-books.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/159147093590377321/posts/default/6301407288575745552'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/159147093590377321/posts/default/6301407288575745552'/><link rel='alternate' type='text/html' href='http://gsmsecurity.blogspot.com/2009/05/best-free-gsm-books.html' title='Best Free GSM Books'/><author><name>Imran Aziz</name><uri>http://www.blogger.com/profile/16311802287455383093</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-159147093590377321.post-5995538547858530257</id><published>2009-05-21T00:31:00.000+06:00</published><updated>2009-05-21T00:42:40.127+06:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='logical channel'/><category scheme='http://www.blogger.com/atom/ns#' term='channels'/><category scheme='http://www.blogger.com/atom/ns#' term='GSM'/><category scheme='http://www.blogger.com/atom/ns#' term='physical channel'/><category scheme='http://www.blogger.com/atom/ns#' term='control channel'/><title type='text'>GSM Physical and Logical Channels</title><content type='html'>&lt;span style="font-weight: bold; font-style: italic;"&gt;Physical Channels&lt;/span&gt;:&lt;br /&gt;&lt;br /&gt;A physical channel is specified by a specific time slot in a specific channel&lt;br /&gt;carrier frequency&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight: bold; font-style: italic;"&gt;logical channels:&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;run over a physical channel, but not necessarily in all its time slots&lt;br /&gt;are classified into traffic channels and control channels&lt;br /&gt;have to be managed: set up, maintenance, tear down&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight: bold; font-style: italic;"&gt;Control channels&lt;/span&gt;:&lt;br /&gt;&lt;br /&gt;Control channels are interspersed with traffic channels in well-specified&lt;br /&gt;ways (e.g. every 26 TDMA frames a logical channel gets bandwidth in a&lt;br /&gt;physical channel)&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/159147093590377321-5995538547858530257?l=gsmsecurity.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://gsmsecurity.blogspot.com/feeds/5995538547858530257/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://gsmsecurity.blogspot.com/2009/05/gsm-physical-and-logical-channels.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/159147093590377321/posts/default/5995538547858530257'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/159147093590377321/posts/default/5995538547858530257'/><link rel='alternate' type='text/html' href='http://gsmsecurity.blogspot.com/2009/05/gsm-physical-and-logical-channels.html' title='GSM Physical and Logical Channels'/><author><name>Imran Aziz</name><uri>http://www.blogger.com/profile/16311802287455383093</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-159147093590377321.post-3455086234836622560</id><published>2009-05-20T00:24:00.004+06:00</published><updated>2009-05-20T00:43:49.255+06:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='KASUMI'/><title type='text'>Best PDF Documents to Understand the Encryption Algorithms</title><content type='html'>For more information about the encryption and encryption algorithms, copy and paste these links into browser:&lt;br /&gt;&lt;br /&gt;http://www.etsi.org/website/document/algorithms/ts_135202v070000p.pdf&lt;br /&gt;&lt;br /&gt;http://cryptome.org/gsm-crack-bbk.pdf&lt;br /&gt;&lt;br /&gt;http://www.cs.technion.ac.il/users/wwwb/cgi-bin/tr-get.cgi/2006/CS/CS-2006-07.pdf&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/159147093590377321-3455086234836622560?l=gsmsecurity.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://gsmsecurity.blogspot.com/feeds/3455086234836622560/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://gsmsecurity.blogspot.com/2009/05/for-more-information-about-encryption.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/159147093590377321/posts/default/3455086234836622560'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/159147093590377321/posts/default/3455086234836622560'/><link rel='alternate' type='text/html' href='http://gsmsecurity.blogspot.com/2009/05/for-more-information-about-encryption.html' title='Best PDF Documents to Understand the Encryption Algorithms'/><author><name>Imran Aziz</name><uri>http://www.blogger.com/profile/16311802287455383093</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-159147093590377321.post-272488793739718594</id><published>2009-05-20T00:13:00.001+06:00</published><updated>2009-05-20T00:15:16.924+06:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='KASUMI'/><category scheme='http://www.blogger.com/atom/ns#' term='A5/1'/><category scheme='http://www.blogger.com/atom/ns#' term='A5/3'/><category scheme='http://www.blogger.com/atom/ns#' term='3G'/><title type='text'>A5/3 or KASUMI Encryption</title><content type='html'>&lt;p&gt;In &lt;a href="http://en.wikipedia.org/wiki/Cryptography" title="Cryptography"&gt;cryptography&lt;/a&gt;, &lt;b&gt;KASUMI&lt;/b&gt;, also termed &lt;b&gt;A5/3&lt;/b&gt;, is a &lt;a href="http://en.wikipedia.org/wiki/Block_cipher" title="Block cipher"&gt;block cipher&lt;/a&gt; used in the &lt;a href="http://en.wikipedia.org/wiki/Confidentiality" title="Confidentiality"&gt;confidentiality&lt;/a&gt; (&lt;i&gt;f8&lt;/i&gt;) and &lt;a href="http://en.wikipedia.org/wiki/Integrity" title="Integrity"&gt;integrity&lt;/a&gt; algorithms (&lt;i&gt;f9&lt;/i&gt;) for &lt;a href="http://en.wikipedia.org/wiki/3GPP" title="3GPP"&gt;3GPP&lt;/a&gt; &lt;a href="http://en.wikipedia.org/wiki/Mobile_phone" title="Mobile phone"&gt;mobile communications&lt;/a&gt;. A number of serious weaknesses in the cipher have been identified.&lt;/p&gt; &lt;p&gt;KASUMI was designed by the &lt;a href="http://en.wikipedia.org/w/index.php?title=Security_Algorithms_Group_of_Experts&amp;amp;action=edit&amp;amp;redlink=1" class="new" title="Security Algorithms Group of Experts (page does not exist)"&gt;Security Algorithms Group of Experts&lt;/a&gt; (SAGE), part of the European standards body &lt;a href="http://en.wikipedia.org/wiki/ETSI" title="ETSI" class="mw-redirect"&gt;ETSI&lt;/a&gt;. Rather than invent a cipher from scratch, SAGE selected an existing algorithm, &lt;a href="http://en.wikipedia.org/wiki/MISTY1" title="MISTY1"&gt;MISTY1&lt;/a&gt;, and optimised it slightly for implementation in hardware. Hence, MISTY1 and KASUMI are very similar — &lt;i&gt;kasumi&lt;/i&gt; (霞) is the &lt;a href="http://en.wikipedia.org/wiki/Japanese_language" title="Japanese language"&gt;Japanese&lt;/a&gt; word for "mist" — and the cryptanalysis of one is likely to be readily adaptable to the other. KASUMI maintains an efficient implementation in software.&lt;/p&gt; &lt;p&gt;KASUMI has a &lt;a href="http://en.wikipedia.org/wiki/Block_size_%28cryptography%29" title="Block size (cryptography)"&gt;block size&lt;/a&gt; of 64 bits and a &lt;a href="http://en.wikipedia.org/wiki/Key_size" title="Key size"&gt;key size&lt;/a&gt; of 128 bits. It is a &lt;a href="http://en.wikipedia.org/wiki/Feistel_cipher" title="Feistel cipher"&gt;Feistel cipher&lt;/a&gt; with eight rounds, and like MISTY1 and &lt;a href="http://en.wikipedia.org/w/index.php?title=MISTY2&amp;amp;action=edit&amp;amp;redlink=1" class="new" title="MISTY2 (page does not exist)"&gt;MISTY2&lt;/a&gt;, it has a recursive structure, with subcomponents also having a Feistel-like form.&lt;/p&gt; &lt;p&gt;In 2001, an &lt;a href="http://en.wikipedia.org/wiki/Impossible_differential_cryptanalysis" title="Impossible differential cryptanalysis"&gt;impossible differential attack&lt;/a&gt; on six rounds of KASUMI was presented by Kühn (2001).&lt;/p&gt; &lt;p&gt;In 2003 Elad Barkan, &lt;a href="http://en.wikipedia.org/wiki/Eli_Biham" title="Eli Biham"&gt;Eli Biham&lt;/a&gt; and Nathan Keller demonstrated attacks against A5/1 and A5/2, that allow attackers to tap GSM mobile phone conversations and decrypt them either in real-time, or at any later time. Protocol weaknesses allow recovery of the key, but the KASUMI algorithm is unaffected in itself.&lt;/p&gt; &lt;p&gt;In 2005, Israeli researchers &lt;a href="http://en.wikipedia.org/wiki/Eli_Biham" title="Eli Biham"&gt;Eli Biham&lt;/a&gt;, Orr Dunkelman and Nathan Keller published a &lt;a href="http://en.wikipedia.org/wiki/Related-key_attack" title="Related-key attack"&gt;related-key&lt;/a&gt; &lt;a href="http://en.wikipedia.org/wiki/Boomerang_attack" title="Boomerang attack"&gt;rectangle (boomerang) attack&lt;/a&gt; on KASUMI that can break all 8 rounds faster than exhaustive search. The attack requires 2&lt;sup&gt;54.6&lt;/sup&gt; chosen plaintexts, each of which has been encrypted under one of four related keys, and has a time complexity equivalent to 2&lt;sup&gt;76.1&lt;/sup&gt; KASUMI encryptions. While this is not a practical attack, it invalidates some proofs about the security of the 3GPP protocols that had relied on the presumed strength of KASUMI.&lt;/p&gt; &lt;p&gt;In 2006, &lt;a href="http://en.wikipedia.org/w/index.php?title=Elad_Barkan&amp;amp;action=edit&amp;amp;redlink=1" class="new" title="Elad Barkan (page does not exist)"&gt;Elad Barkan&lt;/a&gt;, &lt;a href="http://en.wikipedia.org/wiki/Eli_Biham" title="Eli Biham"&gt;Eli Biham&lt;/a&gt;, &lt;a href="http://en.wikipedia.org/w/index.php?title=Nathan_Keller&amp;amp;action=edit&amp;amp;redlink=1" class="new" title="Nathan Keller (page does not exist)"&gt;Nathan Keller&lt;/a&gt; published the full version of their 2003 paper, with attacks against A5/X Ciphers. &lt;sup id="cite_ref-0" class="reference"&gt;&lt;a href="http://en.wikipedia.org/wiki/A5/3#cite_note-0" title=""&gt;&lt;span&gt;[&lt;/span&gt;1&lt;span&gt;]&lt;/span&gt;&lt;/a&gt;&lt;/sup&gt;&lt;/p&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/159147093590377321-272488793739718594?l=gsmsecurity.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://gsmsecurity.blogspot.com/feeds/272488793739718594/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://gsmsecurity.blogspot.com/2009/05/a53-or-kasumi-encryption.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/159147093590377321/posts/default/272488793739718594'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/159147093590377321/posts/default/272488793739718594'/><link rel='alternate' type='text/html' href='http://gsmsecurity.blogspot.com/2009/05/a53-or-kasumi-encryption.html' title='A5/3 or KASUMI Encryption'/><author><name>Imran Aziz</name><uri>http://www.blogger.com/profile/16311802287455383093</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-159147093590377321.post-1072621640903837032</id><published>2009-05-19T23:48:00.000+06:00</published><updated>2009-05-20T00:01:38.573+06:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='A5/1'/><category scheme='http://www.blogger.com/atom/ns#' term='GSM'/><category scheme='http://www.blogger.com/atom/ns#' term='A5/2'/><category scheme='http://www.blogger.com/atom/ns#' term='encryption'/><category scheme='http://www.blogger.com/atom/ns#' term='security'/><category scheme='http://www.blogger.com/atom/ns#' term='privacy'/><title type='text'>What are A5/1 &amp; A5/2 Encryptions</title><content type='html'>&lt;div style="text-align: justify;"&gt;&lt;b&gt;A5/1&lt;/b&gt; is a &lt;a href="http://en.wikipedia.org/wiki/Stream_cipher" title="Stream cipher"&gt;stream cipher&lt;/a&gt; used to provide over-the-air communication &lt;a href="http://en.wikipedia.org/wiki/Privacy" title="Privacy"&gt;privacy&lt;/a&gt; in the &lt;a href="http://en.wikipedia.org/wiki/Global_System_for_Mobile_Communications" title="Global System for Mobile Communications" class="mw-redirect"&gt;GSM&lt;/a&gt; &lt;a href="http://en.wikipedia.org/wiki/Cell_phone" title="Cell phone" class="mw-redirect"&gt;cellular telephone&lt;/a&gt; standard. It was initially kept secret, but became public knowledge through leaks and &lt;a href="http://en.wikipedia.org/wiki/Reverse_engineering" title="Reverse engineering"&gt;reverse engineering&lt;/a&gt;. A number of serious weaknesses in the cipher have been identified.&lt;/div&gt;&lt;p style="text-align: justify;"&gt;A5/1 is used in &lt;a href="http://en.wikipedia.org/wiki/Europe" title="Europe"&gt;Europe&lt;/a&gt; and the United States. &lt;a href="http://en.wikipedia.org/wiki/A5/2" title="A5/2"&gt;A5/2&lt;/a&gt; was a deliberate weakening of the algorithm for certain export regions.&lt;sup id="cite_ref-0" class="reference"&gt;&lt;a href="http://en.wikipedia.org/wiki/A5/1#cite_note-0" title=""&gt;&lt;span&gt;[&lt;/span&gt;1&lt;span&gt;]&lt;/span&gt;&lt;/a&gt;&lt;/sup&gt; A5/1 was developed in 1987, when GSM was not yet considered for use outside Europe, and &lt;a href="http://en.wikipedia.org/wiki/A5/2" title="A5/2"&gt;A5/2&lt;/a&gt; was developed in 1989. Both were initially kept secret. However, the general design was leaked in 1994, and the algorithms were entirely reverse engineered in 1999 by &lt;a href="http://en.wikipedia.org/w/index.php?title=Marc_Briceno&amp;amp;action=edit&amp;amp;redlink=1" class="new" title="Marc Briceno (page does not exist)"&gt;Marc Briceno&lt;/a&gt; from a GSM telephone. In 2000, around 130 million GSM customers relied on A5/1 to protect the confidentiality of their voice communications.&lt;/p&gt;&lt;div style="text-align: justify;"&gt; &lt;/div&gt;&lt;p style="text-align: justify;"&gt;Security researcher &lt;a href="http://en.wikipedia.org/wiki/Ross_Anderson" title="Ross Anderson" class="mw-redirect"&gt;Ross Anderson&lt;/a&gt; reported in 1994 that "there was a terrific row between the &lt;a href="http://en.wikipedia.org/wiki/NATO" title="NATO"&gt;NATO&lt;/a&gt; &lt;a href="http://en.wikipedia.org/wiki/SIGINT" title="SIGINT" class="mw-redirect"&gt;signal intelligence agencies&lt;/a&gt; in the mid 1980s over whether GSM encryption should be strong or not. The Germans said it should be, as they shared a long border with the &lt;a href="http://en.wikipedia.org/wiki/Warsaw_Pact" title="Warsaw Pact"&gt;Warsaw Pact&lt;/a&gt;; but the other countries didn't feel this way, and the algorithm as now fielded is a French design."&lt;sup id="cite_ref-1" class="reference"&gt;&lt;a href="http://en.wikipedia.org/wiki/A5/1#cite_note-1" title=""&gt;&lt;span&gt;[&lt;/span&gt;2&lt;span&gt;]&lt;/span&gt;&lt;/a&gt;&lt;/sup&gt;&lt;/p&gt;&lt;div style="text-align: justify;"&gt;A number of attacks on A5/1 have been published. Some require an expensive preprocessing stage after which the cipher can be attacked in minutes or seconds. Until recently, the weaknesses have been passive attacks using the &lt;a href="http://en.wikipedia.org/wiki/Known_plaintext" title="Known plaintext" class="mw-redirect"&gt;known plaintext&lt;/a&gt; assumption. In 2003, more serious weaknesses were identified which can be exploited in the &lt;a href="http://en.wikipedia.org/wiki/Ciphertext_only_attack" title="Ciphertext only attack" class="mw-redirect"&gt;ciphertext-only scenario&lt;/a&gt;, or by an active attacker. In 2006 Elad Barkan, &lt;a href="http://en.wikipedia.org/wiki/Eli_Biham" title="Eli Biham"&gt;Eli Biham&lt;/a&gt; and Nathan Keller demonstrated attacks against A5/1, &lt;a href="http://en.wikipedia.org/wiki/A5/3" title="A5/3" class="mw-redirect"&gt;A5/3&lt;/a&gt;, or even GPRS that allow attackers to tap GSM mobile phone conversations and decrypt them either in real-time, or at any later time.In 2003, Barkan  &lt;em&gt;et al.&lt;/em&gt; published several attacks on GSM encryption.&lt;sup id="cite_ref-7" class="reference"&gt;&lt;a href="http://en.wikipedia.org/wiki/A5/1#cite_note-7" title=""&gt;&lt;span&gt;[&lt;/span&gt;8&lt;span&gt;]&lt;/span&gt;&lt;/a&gt;&lt;/sup&gt; The first is an active attack. GSM phones can be convinced to use the much weaker &lt;a href="http://en.wikipedia.org/wiki/A5/2" title="A5/2"&gt;A5/2&lt;/a&gt; cipher briefly. A5/2 can be broken easily, and the phone uses the same key as for the stronger A5/1 algorithm. A second attack on A5/1 is outlined, a &lt;a href="http://en.wikipedia.org/wiki/Ciphertext-only" title="Ciphertext-only" class="mw-redirect"&gt;ciphertext-only&lt;/a&gt; time-memory tradeoff attack which requires a large amount of precomputation.&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/159147093590377321-1072621640903837032?l=gsmsecurity.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://gsmsecurity.blogspot.com/feeds/1072621640903837032/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://gsmsecurity.blogspot.com/2009/05/what-are-a51-a52-encryptions.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/159147093590377321/posts/default/1072621640903837032'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/159147093590377321/posts/default/1072621640903837032'/><link rel='alternate' type='text/html' href='http://gsmsecurity.blogspot.com/2009/05/what-are-a51-a52-encryptions.html' title='What are A5/1 &amp; A5/2 Encryptions'/><author><name>Imran Aziz</name><uri>http://www.blogger.com/profile/16311802287455383093</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-159147093590377321.post-5039139628104006382</id><published>2009-05-19T20:11:00.000+06:00</published><updated>2009-05-19T20:13:46.242+06:00</updated><title type='text'>GSM Encryption Algorithms</title><content type='html'>A partial source code implementation of the GSM A5 algorithm was leaked to the Internet in June, 1994. More recently there have been rumors that this implementation was an early design and bears little resemblance to the A5 algorithm currently deployed. Nevertheless, insight into the underlying design theory can be gained by analyzing the available information. The details of this implementation, as well as some documented facts about A5, are summarized below:&lt;br /&gt;A5 is a stream cipher consisting of three clock-controlled LFSRs of degree 19, 22, and 23.&lt;br /&gt;The clock control is a threshold function of the middle bits of each of the three shift registers.&lt;br /&gt;The sum of the degrees of the three shift registers is 64. The 64-bit session key is used to initialize the contents of the shift registers.&lt;br /&gt;The 22-bit TDMA frame number is fed into the shift registers.&lt;br /&gt;Two 114-bit keystreams are produced for each TDMA frame, which are XOR-ed with the uplink and downlink traffic channels.&lt;br /&gt;It is rumored that the A5 algorithm has an "effective" key length of 40 bits.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/159147093590377321-5039139628104006382?l=gsmsecurity.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://gsmsecurity.blogspot.com/feeds/5039139628104006382/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://gsmsecurity.blogspot.com/2009/05/gsm-encryption-algorithms.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/159147093590377321/posts/default/5039139628104006382'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/159147093590377321/posts/default/5039139628104006382'/><link rel='alternate' type='text/html' href='http://gsmsecurity.blogspot.com/2009/05/gsm-encryption-algorithms.html' title='GSM Encryption Algorithms'/><author><name>Imran Aziz</name><uri>http://www.blogger.com/profile/16311802287455383093</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-159147093590377321.post-2274911522723888324</id><published>2009-05-19T18:10:00.001+06:00</published><updated>2009-05-19T18:14:16.063+06:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='camera'/><category scheme='http://www.blogger.com/atom/ns#' term='axis'/><category scheme='http://www.blogger.com/atom/ns#' term='security'/><category scheme='http://www.blogger.com/atom/ns#' term='hack'/><title type='text'>How to hack network security cameras?</title><content type='html'>Adopt the following process and hack the network security cameras:&lt;br /&gt;&lt;br /&gt;1. Go to Google.com&lt;br /&gt;2. Type&lt;br /&gt;&lt;br /&gt;             intitle:"Live View /-AXIS"&lt;br /&gt;&lt;br /&gt;and click search&lt;br /&gt;&lt;br /&gt;3. Go to the searched links and control the security cameras working in the world&lt;br /&gt;&lt;br /&gt;ENJOY IT&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/159147093590377321-2274911522723888324?l=gsmsecurity.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://gsmsecurity.blogspot.com/feeds/2274911522723888324/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://gsmsecurity.blogspot.com/2009/05/how-to-hack-network-security-cameras.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/159147093590377321/posts/default/2274911522723888324'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/159147093590377321/posts/default/2274911522723888324'/><link rel='alternate' type='text/html' href='http://gsmsecurity.blogspot.com/2009/05/how-to-hack-network-security-cameras.html' title='How to hack network security cameras?'/><author><name>Imran Aziz</name><uri>http://www.blogger.com/profile/16311802287455383093</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-159147093590377321.post-4172901557015345387</id><published>2009-05-19T17:28:00.000+06:00</published><updated>2009-05-19T17:32:41.696+06:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='A3'/><category scheme='http://www.blogger.com/atom/ns#' term='A8'/><title type='text'>Have the A3 and A8 algorithms been broken?</title><content type='html'>&lt;p&gt;Most GSM providers use a version of COMP128 for both the A3 authentication algorithm and the A8 key generation algorithm.&lt;/p&gt;  &lt;p&gt;Ian Goldberg and David Wagner of the University of California at Berkeley demonstrated that all A8 implementations they looked at, including the few that did not use COMP128, were deliberately weakened. The A8 algorithm takes a 64-bit key, but ten key bits were set to zero. The attack on the A8 algorithm demonstrated by Goldberg and Wagner takes just 2^19 queries to the GSM SIM *Subscriber Identity Module), which takes roughly 8 hours.&lt;/p&gt;  &lt;p&gt;Josyula R. Rao, Pankaj Rohatgi and Helmut Scherzer of IBM and Stephane Tinguely of the Swiss Federal Institute of Technology have published &lt;a href="javascript:var%20handle=window.open('http://www.research.ibm.com/intsec/gsm.html')"&gt;Partitioning Attacks: Or How to Rapidly Clone Some GSM Cards&lt;/a&gt; which shows a method by which COMP128 can be broken in less than a minute.&lt;/p&gt;  &lt;p&gt;The COMP128-2 and COMP128-3 algorithms have been developed to address the security issues of COMP128-1. COMP128-2 and COMP128-3 are secret algorithms which have not been subject to cryptanalysis. COMP128-3 fixes the issue where 10 bits of the Session Key (Kc) were set to zero.&lt;/p&gt;  &lt;p&gt;GSM network operators are slowly migrating from COMP128 (also known as COMP128-1) to COMP28-2 or COMP128-3. Because the A3 and A8 algorithms are stored in the Subscriber Identity Module, this requires changing the GSM subscribers SIM cards.&lt;/p&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/159147093590377321-4172901557015345387?l=gsmsecurity.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://gsmsecurity.blogspot.com/feeds/4172901557015345387/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://gsmsecurity.blogspot.com/2009/05/have-a3-and-a8-algorithms-been-broken.html#comment-form' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/159147093590377321/posts/default/4172901557015345387'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/159147093590377321/posts/default/4172901557015345387'/><link rel='alternate' type='text/html' href='http://gsmsecurity.blogspot.com/2009/05/have-a3-and-a8-algorithms-been-broken.html' title='Have the A3 and A8 algorithms been broken?'/><author><name>Imran Aziz</name><uri>http://www.blogger.com/profile/16311802287455383093</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-159147093590377321.post-1520930813501639499</id><published>2009-05-19T17:24:00.000+06:00</published><updated>2009-05-19T17:27:09.482+06:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='Ki'/><category scheme='http://www.blogger.com/atom/ns#' term='Kc'/><category scheme='http://www.blogger.com/atom/ns#' term='GSM'/><category scheme='http://www.blogger.com/atom/ns#' term='security'/><category scheme='http://www.blogger.com/atom/ns#' term='authentication'/><category scheme='http://www.blogger.com/atom/ns#' term='SRES'/><title type='text'>How do Authentication and Key generation work in a GSM network?</title><content type='html'>&lt;p&gt;Encryption in the GSM network utilizes a Challenge/Response mechanism.&lt;/p&gt;  &lt;ol&gt;&lt;li&gt;The Mobile Station (MS) signs into the network. &lt;/li&gt;&lt;li&gt;The Mobile Services Switching Center (MSC) requests 5 triples from the Home Location Register (HLR). &lt;/li&gt;&lt;li&gt;The Home Location Register creates five triples utilizing the A8 algorithm.  These five triples each contain:  &lt;ul&gt;&lt;li&gt;A 128-bit random challenge (RAND) &lt;/li&gt;&lt;li&gt;A 32-bit matching Signed Response (SRES) &lt;/li&gt;&lt;li&gt;A 64-bit ciphering key used as a Session Key (Kc). &lt;/li&gt;&lt;/ul&gt; &lt;/li&gt;&lt;li&gt;The Home Location Register sends the Mobile Services Switching Center the five triples. &lt;/li&gt;&lt;li&gt;The Mobile Services Switching Center sends the random challenge from the first triple to the Base Transceiver Station (BTS). &lt;/li&gt;&lt;li&gt;The Base Transceiver Station sends the random challenge from the first triple to the Mobile Station. &lt;/li&gt;&lt;li&gt;The Mobile Station receives the random challenge from the Base Transceiver Station and encrypts it with the Individual Subscriber Authentication Key (Ki) assigned to the Mobile Station utilizing the A3 algorithm. &lt;/li&gt;&lt;li&gt;The Mobile Station sends the Signed Response to the Base Transceiver Station. &lt;/li&gt;&lt;li&gt;The Base Transceiver Station sends the Signed Response to the Mobile Services Switching Center. &lt;/li&gt;&lt;li&gt;The Mobile Services Switching Center verifies the Signed Response. &lt;/li&gt;&lt;li&gt;The Mobile Station generates a Session Key (Kc) utilizing the A8 algorithm, the Individual Subscriber Authentication Key (Ki) assigned to the Mobile Station, and the random challenge received from the Base Transceiver Station. &lt;/li&gt;&lt;li&gt;The Mobile Station sends the Session Key (Kc) to the Base Transceiver Station. &lt;/li&gt;&lt;li&gt;The Mobile Services Switching Center sends the Session Key (Kc) to the Base Transceiver Station. &lt;/li&gt;&lt;li&gt;The Base Transceiver Station receives the Session Key (Kc) from the Mobile Services Switching Center. &lt;/li&gt;&lt;li&gt;The Base Transceiver Station receives the Session Key (Kc) from the Mobile Station. &lt;/li&gt;&lt;li&gt;The Base Transceiver Station verifies the Session Keys from the Mobile Station and the Mobile Services switching Center. &lt;/li&gt;&lt;li&gt;The A5 algorithm is initialized with the Session Key (Kc) and the number of the frame to be encrypted. &lt;/li&gt;&lt;li&gt;Over-the-air communication channel between the Mobile Station and Base Transceiver Station can now be encrypted utilizing the A5 algorithm. &lt;/li&gt;&lt;/ol&gt;  &lt;p&gt;This process authenticates the GSM Mobile Station (MS) to the GSM network. One known security limitation of GSM networks is that the GSM network is never authenticated by the GSM Mobile Station (MS).&lt;/p&gt;  &lt;p&gt;This one-way authentication makes it possible for an attacker to pretend to be a GSM network provider.&lt;/p&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/159147093590377321-1520930813501639499?l=gsmsecurity.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://gsmsecurity.blogspot.com/feeds/1520930813501639499/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://gsmsecurity.blogspot.com/2009/05/how-do-authentication-and-key.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/159147093590377321/posts/default/1520930813501639499'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/159147093590377321/posts/default/1520930813501639499'/><link rel='alternate' type='text/html' href='http://gsmsecurity.blogspot.com/2009/05/how-do-authentication-and-key.html' title='How do Authentication and Key generation work in a GSM network?'/><author><name>Imran Aziz</name><uri>http://www.blogger.com/profile/16311802287455383093</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-159147093590377321.post-3960906964200840881</id><published>2009-05-19T17:20:00.001+06:00</published><updated>2009-05-20T00:22:41.578+06:00</updated><title type='text'>How do Authentication and Key generation work in a GSM network?</title><content type='html'>&lt;p&gt;Encryption in the GSM network utilizes a Challenge/Response mechanism.&lt;/p&gt;  &lt;ol&gt;&lt;li&gt;The Mobile Station (MS) signs into the network. &lt;/li&gt;&lt;li&gt;The Mobile Services Switching Center (MSC) requests 5 triples from the Home Location Register (HLR). &lt;/li&gt;&lt;li&gt;The Home Location Register creates five triples utilizing the A8 algorithm.  These five triples each contain:  &lt;ul&gt;&lt;li&gt;A 128-bit random challenge (RAND) &lt;/li&gt;&lt;li&gt;A 32-bit matching Signed Response (SRES) &lt;/li&gt;&lt;li&gt;A 64-bit ciphering key used as a Session Key (Kc). &lt;/li&gt;&lt;/ul&gt; &lt;/li&gt;&lt;li&gt;The Home Location Register sends the Mobile Services Switching Center the five triples. &lt;/li&gt;&lt;li&gt;The Mobile Services Switching Center sends the random challenge from the first triple to the Base Transceiver Station (BTS). &lt;/li&gt;&lt;li&gt;The Base Transceiver Station sends the random challenge from the first triple to the Mobile Station. &lt;/li&gt;&lt;li&gt;The Mobile Station receives the random challenge from the Base Transceiver Station and encrypts it with the Individual Subscriber Authentication Key (Ki) assigned to the Mobile Station utilizing the A3 algorithm. &lt;/li&gt;&lt;li&gt;The Mobile Station sends the Signed Response to the Base Transceiver Station. &lt;/li&gt;&lt;li&gt;The Base Transceiver Station sends the Signed Response to the Mobile Services Switching Center. &lt;/li&gt;&lt;li&gt;The Mobile Services Switching Center verifies the Signed Response. &lt;/li&gt;&lt;li&gt;The Mobile Station generates a Session Key (Kc) utilizing the A8 algorithm, the Individual Subscriber Authentication Key (Ki) assigned to the Mobile Station, and the random challenge received from the Base Transceiver Station. &lt;/li&gt;&lt;li&gt;The Mobile Station sends the Session Key (Kc) to the Base Transceiver Station. &lt;/li&gt;&lt;li&gt;The Mobile Services Switching Center sends the Session Key (Kc) to the Base Transceiver Station. &lt;/li&gt;&lt;li&gt;The Base Transceiver Station receives the Session Key (Kc) from the Mobile Services Switching Center. &lt;/li&gt;&lt;li&gt;The Base Transceiver Station receives the Session Key (Kc) from the Mobile Station. &lt;/li&gt;&lt;li&gt;The Base Transceiver Station verifies the Session Keys from the Mobile Station and the Mobile Services switching Center. &lt;/li&gt;&lt;li&gt;The A5 algorithm is initialized with the Session Key (Kc) and the number of the frame to be encrypted. &lt;/li&gt;&lt;li&gt;Over-the-air communication channel between the Mobile Station and Base Transceiver Station can now be encrypted utilizing the A5 algorithm. &lt;/li&gt;&lt;/ol&gt;  &lt;p&gt;This process authenticates the GSM Mobile Station (MS) to the GSM network. One known security limitation of GSM networks is that the GSM network is never authenticated by the GSM Mobile Station (MS).&lt;/p&gt;  &lt;p&gt;This one-way authentication makes it possible for an attacker to pretend to be a GSM network provider.&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/159147093590377321-3960906964200840881?l=gsmsecurity.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://gsmsecurity.blogspot.com/feeds/3960906964200840881/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://gsmsecurity.blogspot.com/2009/05/how-do-authentication-and-key_19.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/159147093590377321/posts/default/3960906964200840881'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/159147093590377321/posts/default/3960906964200840881'/><link rel='alternate' type='text/html' href='http://gsmsecurity.blogspot.com/2009/05/how-do-authentication-and-key_19.html' title='How do Authentication and Key generation work in a GSM network?'/><author><name>Imran Aziz</name><uri>http://www.blogger.com/profile/16311802287455383093</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry></feed>
