3 ms·
There's also the problem that when communications companies think of security, they may be thinking of "revenue protection" more than customer privacy (that is,
by schoen 12y ago
There's also the problem that when communications companies think of security, they may be thinking of "revenue protection" more than customer privacy (that is, making sure that customers have to pay to communicate, and that they get billed accurately).
Ross Anderson liked to point out that the crypto that some cell phones used to discourage you from using aftermarket batteries was stronger than the crypto they used to protect your voice calls over the air. He's also suggested that the crypto in GSM ended up more focused on subscriber authentication than on voice privacy.
There is also now a source for the notion that governments pressured the designers of GSM to make it not provide strong cryptographic privacy:
http://www.aftenposten.no/nyheter/uriks/Sources-We-were-pressured-to-weaken-the-mobile-security-in-the-80s-7413285.html http://www.aftenposten.no/nyheter/uriks/Sources-We-were-pres...
Here is a sad thing: Governments are STILL pressuring the designers of GSM to make it not provide strong cryptographic privacy. Like, today. We got some documents from ETSI only a couple of years ago showing that they are designing a cryptographic backdoor mode for the official GSM end-to-end voice encryption, which isn't even deployed yet. The use of the backdoor mode will be optional according to carriers' view of their jurisdictional obligations.
Sorry, that last part is less on-topic for this thread. But in the big picture, I'm sure the people who are involved in those efforts are not making corresponding compromises in the billing and revenue-protection areas.