Slashdot Mirror
How To Compete With NSA By Hacking a Verizon Network Extender
New submitter Anita Hunt (lissnup) writes "This snooping hack-in-a-backpack could become a hot Summer accessory, since Reuters reported that 'researchers at iSec hacked into a Verizon network extender, which anyone can buy online, and turned it into a cell phone tower (video interview) small enough to fit inside a backpack capable of capturing and intercepting all calls, text messages and data sent by mobile devices within range.'"
"This is ordinary people intercepting... ordinary people". A nice,, bitter subversion of the "power to the people" concept ?
Religous speak to God. Insane are spoken to by God. When all shut up, one can finally hear Shostakovich in peace
In the good old bad old days, all you needed to butt into a phone conversation was a Buttinsky phone (linesman test set). Nowadays, you need a whole backpack full of equipment a laptop computer and heavy batteries and we call this progress?
Excuse me, but please get off my Pennisetum Clandestinum, eh!
Why would you need to sync your phone to the station to get it to work, let's just send unencrypted communication all over the place.
We should be careful in just encouraging encrypted communication, because the usual interpretations of this provide no security at all, and were rejected back in the ARPAnet days of the 1960s by the security advisers.
The usual interpretation of "encrypted communication", of course, is the frequent suggestion that "the Internet" itself should do encryption. This is especially suggested by people who've figured out that the average user doesn't stand much of a chance of doing it right, with modern comm software.
But having "the Internet" do the encryption actually means that the encryption is done by your comm supplier, i.e. your ISP or phone company. What this means is that your comm supplier is the one who also does the decryption, so they have complete access to everything. The recent stories about the close ties between government security agencies and the comm companies show that this would be no security at all.
What was decided back in the 1960s, and what anyone with a basic understanding of security will agree with, is that the low-level comm stuff shouldn't be burdened with any security measures. They are simply a waste of cpu time, since they make your messages accessible to the people who run the low-level comm stuff. The low-level stuff should therefore be tasked simply with getting the bits across as fast as possible. To qualify as secure, any encryption must be handled by the two end-points in a conversation.
Note that this doesn't mean that the (human) end users need to be the ones doing the encryption. What it means is that the encryption software must be running on the piece of hardware that they're using, not by anything further away in the connection.
Of course, then you have the next problem, of preventing spy software from being installed on the hardware at either end. But that's a different issue.
The primary understanding is that we should insist that "encrypted communication" be done only end-to-end. Anything else inherently makes your info available to whoever owns the hardware that's running the encryption software. (And it makes the whole comm system run slower, since encryption software does use cpu time, and if it's not in the end systems, it's 100% a waste of that cpu time.)
The major use-level issue is whether we can create encryption software that runs in the users' gadgets, and which the users can actually use correctly, and which won't be compromised by builtin backdoors such as keyloggers that were installed by the comm companies.
Those who do study history are doomed to stand helplessly by while everyone else repeats it.
Actually, there would be quite a bit of security against non-governmental attackers and those working for foreign governments.
And while it is the governmental ones that scare us for having a potential for abuse, it is those others that have done actual damage to millions of computers and hurt millions of people already — through spamming, identity theft, and spying.
I, for one, would've been glad to be rid of those, even if Uncle Sam's fishing expeditions remain a threat.
In Soviet Washington the swamp drains you.
Not necessarily. You could just have the initial key exchange built into the initial handshake, e.g. like this:
The SYN packet contains the public key certificate of the client.
The SYN/ACK packet contains the public key certificate of the server, and a hash of the client's certificate signed with the server's private key.
The final ACK packet contains a hash of the certificate the server sent, signed with the client's private key.
At this point, the communicating computers know enough about each other to safely encrypt their data stream without any middle man (including the ISP) being able to read the messages. Also, they know that each other computer has the private key for the public key certificate they've sent. All further data then can be encrypted, only the source/destination IP and port need to be unencrypted (because those are needed to route the packets). Since the encryption would already happen at the protocol level, the only thing which would ever go over the lines unencryted would be IP addresses, port numbers and public key certificates.
Of course at this point you did not establish the identity of the server and/or the client, so to prevent MITM attacks you'd need further means to authenticate the server. But the very basic operation of point-to-point encryption of all traffic of a connection can very well be done at the protocol level.
They actually run Linux.
And:
"Verizon Wireless released a Linux software update in March that prevents its network extenders from being compromised in the manner reported by Ritter and DePerry, according to company spokesman David Samberg."
http://www.voanews.com/content/reu-researchers-hack-verizon-device/1701880.html
Redphone (https://whispersystems.org/) does this for free, but unfortunately, it uses data, and only works on Android.
vxWorks, QNX... any number of much smaller, true real time OSes that are a far better fit for such tasks. Of course, they aren't free and the people who know how to program for them aren't cheap.