News for hackers. Stuff that matters.
Re:It's Time to Fix HTTPS by tptacek on Sunday March 27, 2011 @09:08PM (#2376648)
No, it's not. To encrypt data between two parties who don't know each other, both sides have to agree on a key. There is no protocol that does that securely in the presence of a man in the middle without a "tiebreaker"; the tiebreaker SSL PKI uses is certificates.
Re:It's Time to Fix HTTPS by julian37 on Sunday March 27, 2011 @09:27PM (#2376701)
But doesn't (unauthenticated) encryption at least protect against eavesdroppers who don't have the ability to modify the stream, i.e. to mount a MITM attack?
Re:It's Time to Fix HTTPS by caf on Sunday March 27, 2011 @09:54PM (#2376763)
"eavesdroppers who don't have the ability to modify the stream" are a nice fairytale, but they don't really exist in practice, with current network protocols. DNSSEC might change this, once it becomes universal.
Re:It's Time to Fix HTTPS by julian37 on Sunday March 27, 2011 @10:03PM (#2376793)
What about Firesheep users? Surely there are many people who find it a lot easier to just capture some WiFi traffic via libpcap, WireShark or the like than to set up a fake WiFi access point, poison a DNS cache or mount other such attacks that would allow them to actually modify traffic.
Re:It's Time to Fix HTTPS by tptacek on Sunday March 27, 2011 @10:47PM (#2376902)
Why are we talking about defenses that are defeated by just a couple lines of code? Firesheep could use pcap_write in addition to pcap_loop and redirect connections. What's the point of a defense that breaks Firesheep 1.0 only to fall to Firesheep 2.0?
Re:It's Time to Fix HTTPS by julian37 on Sunday March 27, 2011 @11:12PM (#2376971)
Isn't that a bit like saying that it's pointless for policemen to wear bulletproof vests because there could always be a sniper aiming at their head?

Generally speaking, and regardless of today's protocols, surely passive eavesdropping is and will always remain easier to accomplish than actively mounting a MITM attack.

Re:It's Time to Fix HTTPS by tptacek on Sunday March 27, 2011 @11:48PM (#2377058)
No. The opposite is true. It's actually easier to MITM in 2011 than it is to sniff passively; the MITM only needs to play packet games long enough to get the victim to connect to her.
Re:It's Time to Fix HTTPS by julian37 on Sunday March 27, 2011 @11:51PM (#2377064)
Interesting, I didn't realize that. Since you're tptacek I'll take your word for it :-)
Re:It's Time to Fix HTTPS by caf on Sunday March 27, 2011 @11:39PM (#2377037)
The only reason Firesheep doesn't modify traffic is because it doesn't have to. Faking DNS replies or similar would be trivial to add, were it needed.

The vulnerability here isn't "someone running Firesheep" - that's the exploit. The vulnerability here is "an open WiFi network is a completely trusted medium".

Re:It's Time to Fix HTTPS by __david__ on Monday March 28, 2011 @01:23AM (#2377252)
Given the recent EFF story about AT&T shunting all their traffic through NSA computers, I would say it most certainly exists in practice. Basic encryption with no authentication doesn't hold up at all to directed attacks, but it would definitely help with big siphoning attacks that are actually happening right now.
Re:It's Time to Fix HTTPS by tptacek on Monday March 28, 2011 @10:04AM (#2378372)
MITM attacks don't have to be directed. It's not technically challenging to mass-MITM a channel --- but you probably wouldn't do that, because you can just pick "interesting" connections (like, to Google Mail) to intercept.