NEWS: We have created a PRIVATE A5 mailinglist. If you feel you have something to contribute to the project please contact steve [at] segfault.net. The reason for this has been explained on the public mailinglist a5 [at] lists.segfault.net.
NEW: The CCC Camp07 GSM Software Project and A5 Cracking Talk video is available. The final attack and a live demonstration will be given at a selected security conference in March 2008.
All code, information or data [from now on "data"]
available from the GSM Software Project or any other
project linked from this or other pages is owned by the
creator who created the data. The copyright, license
right, distribution right and any other rights lies with
It is prohibitied to use the data without the written agreement of the creator. This included using ideas in other projects (commercial or not commercial).
We are security enthusiasts. Our goal is to implement a system that can crack A5/1. Our
results will be used with the GSM Software Project to demonstrate weaknesses in GSM.
The A5 algorithm has been broken (in theory) in 1998 but it's still widely used. The
mobile operators still insist that the GSM customers (that's you and me!) are protected and
that our data is safe.
Protocol implementation is faulty: An attacker can record all encrypted traffic. If the
attacker gains access to the sim at any point in the future he can decrypt all traffic
sniffed in the past. This works by putting the sim card into a sim reader and running
the gsm_runalgorithm() function on the sim. The sim will decode any traffic without
us knowing the Ki. This attack requires access to the sim for 30 seconds and can
decode any GSM converstation that happened in the past.
I did a quick example to visualize the entroypy. Crypto people love entropy. An easy way
to visualize the entropy is to generate a picture of the relationship between two, three or
four successive numbers generated by the algorithm. Ideally we should not see any
structure. All pixels should be distributed randomly. lcamtufs ISN analyzsis explains more
details about this method.
Now bringing you back...
Does that email address look wrong? Try again with a different email.