3 ms·
A5/3 (Kasumi) is near-on identical to the cyphers used in 3G connections, but you're right, this is the 2G only implementation; so yes, this only affects (appli
by BuildTheRobots 12y ago
A5/3 (Kasumi) is near-on identical to the cyphers used in 3G connections, but you're right, this is the 2G only implementation; so yes, this only affects (applies to) 2G/EDGE/GSM.
I'm absolutely bloody agog that commercial first-world operators have taken until the end of 2014 to actually support this -I think it was ratified into the specification around 2001 if not earlier.
Also, for all you tinfoil wearers out there, you might like the fact that the original specification for A5/3 was altered to make it more hardware friendly. In 2010 it was realized that this actually made it extremely easy [1] to recover the session key (if not in real time) [2].
[1] core2due in a couple of hours easy, see the abstract [2].
[2] http://eprint.iacr.org/2010/013 http://eprint.iacr.org/2010/013
- droopybuns 12y agoA5/3 is a block cipher, 3G connections use a stream cipher. Respectfully, this is not "near-on" identical. http://security.stackexchange.com/questions/334/advantages-and-disadvantages-of-stream-versus-block-ciphers http://security.stackexchange.com/questions/334/advantages-a... Integrating support for these algorithms on the device side ends up being a high hurdle. Doing anything at scale is inevitably harder than you expect it to be. If it was a simple change, people would make it.
- BuildTheRobots 12y agoTHanks for the clarification, I'm obviously getting myself confused somewhere. /me goes back to the documentation.