7 ms·
Eavesdropping Encrypted LTE Calls With ReVoLTE
- wyxuan 6y agoWhats with the alternating caps in the title? Is it to be sarcastic?
- stingraycharles 6y agoFWIW, its not in the title of the article, just the HN title. Mods should change it probably.
- chrisseaton 6y ago* Voice over Long-Term Evolution * Voice over LTE * VoLTE * key-REuse VoLTE * ReVoLTE * Call Me Maybe: Eavesdropping Encrypted LTE Calls With ReVoLTE * Call Me Maybe: EaVesDropPing EnCrypTed LTE Calls with ReVoLTE Researchers are trying to make their work memorable by using marketing techniques like these. I assume the title on HN (which isn't the same as the article) is mocking it.
- kanobo 6y agoThe illustrations are very charming. Here's the android app to test if your station is vulnerable: https://github.com/RUB-SysSec/mobile_sentinel https://github.com/RUB-SysSec/mobile_sentinel
- mNovak 6y agoSeems like an awfully large oversight to reuse the encryption key between subsequent calls. I wonder if this works when leaving voicemail in the second call? Since the approach requires a long call for a long decryption, dialing straight to voicemail would be non-cooperative and avoid alerting the victim until after.
- jschwartzi 6y agoVoicemail goes to a different place and may not even get you routed to the user’s cell.
- microcolonel 6y agoIt's something so stupid I have to imagine it is deliberate.
- tinus_hn 6y agoThe argument typically is that good encryption causes the call setup time to be too long and costs battery life, but this indeed is an exceptionally dumb flaw. Unless you know what you’re doing it’s hard to test for though, and if you know what you’re doing you wouldn’t make this kind of mistake.
- 1231asra 6y agoSomewhat true, but standards could assist developers with adequate test vectors, explanations and reminders why X or Y is important.
- unixhero 6y agoWouldn't you get into massive amounts of trouble for running this on an operators commercial network?
- deleted 6y ago[deleted]