PeterGV
K1PGV
As the poster said, brute forcing DES isn't anything new. Demonstrating this on a RADIO channel is cool, and worthy of a paper, and fun. But nobody who cares about their data has used plain DES for years. Note "DES" is not the same as "3DES" which is widely used.
And... for something like the thousandth time on RR: AES256 *is* approved by the NSA for protection of TOP SECRET information, but -- like every other crypto technique -- it has to be used with other approved mechanisms (such as an appropriate public key exchange method). See the NSA document that makes this crystal clear here.
In any case... I thank the OP for the pointer to this paper. To me, at least, it's VERY interesting stuff. The point of the authors seems to be that P25 (and even Moto radios) weren't really designed with proper security in mind. And this makes sense: People tend to be data security professionals, encryption professionals, or wireless protocol professionals. Few people tend to be ALL those things.
So, like with anything, in P25 there's advantages and disadvantages. You give and you get. Even the same feature can be both an advantage and disadvantage.
Advantage: Not all bits in a voice message need to be received for the voice message to be decoded to intelligible speech. If you're designing a radio system, this is a good thing. You want your subscribers to still get their audio, even when they're running down an alley and getting all sorts of multipath.
Disadvantage: Not all bits in a voice message need to be received for the voice message to be decoded to intelligible speech. If you're concerned about security, this means you can't use "real" block ciphers and you can't perform authentication. OCB mode, which is MOST secure and also gets you authentication, is not possible unless all the preceding data has been received correctly.
ANYhow, the report is darn good. Shows you how security folks can quickly poke holes even in good quality work done by communications protocol experts.
Peter
K1PGV
And... for something like the thousandth time on RR: AES256 *is* approved by the NSA for protection of TOP SECRET information, but -- like every other crypto technique -- it has to be used with other approved mechanisms (such as an appropriate public key exchange method). See the NSA document that makes this crystal clear here.
In any case... I thank the OP for the pointer to this paper. To me, at least, it's VERY interesting stuff. The point of the authors seems to be that P25 (and even Moto radios) weren't really designed with proper security in mind. And this makes sense: People tend to be data security professionals, encryption professionals, or wireless protocol professionals. Few people tend to be ALL those things.
So, like with anything, in P25 there's advantages and disadvantages. You give and you get. Even the same feature can be both an advantage and disadvantage.
Advantage: Not all bits in a voice message need to be received for the voice message to be decoded to intelligible speech. If you're designing a radio system, this is a good thing. You want your subscribers to still get their audio, even when they're running down an alley and getting all sorts of multipath.
Disadvantage: Not all bits in a voice message need to be received for the voice message to be decoded to intelligible speech. If you're concerned about security, this means you can't use "real" block ciphers and you can't perform authentication. OCB mode, which is MOST secure and also gets you authentication, is not possible unless all the preceding data has been received correctly.
ANYhow, the report is darn good. Shows you how security folks can quickly poke holes even in good quality work done by communications protocol experts.
Peter
K1PGV
Last edited: