News for hackers. Stuff that matters.
Re:We need a “/heartbleed.txt” standard, and we need it ASAP by bitJericho on Wednesday April 09, 2014 @10:36AM (#7559504)
Biggest ever hole? Really? Am I the only one that remembers Yahoo placing passwords in the URL of unencrypted pages? I remember having to erase the URL line when people were around for fear of leaking my password.
Re:We need a “/heartbleed.txt” standard, and we need it ASAP by jik on Wednesday April 09, 2014 @10:43AM (#7559559)
I hardly think that a security hole, no matter how large, at a single web site, is on the same magnitude as one security hole that probably impacts the majority of web sites on the internet and could have been taken advantage of completely invisibly for years.
Re:We need a “/heartbleed.txt” standard, and we need it ASAP by Navarr on Wednesday April 09, 2014 @10:50AM (#7559606)
This is a silly, unnecessary standard that will probably not be implemented by anyone.

Saying we need it and we need it now is simply ridiculous.

Re:We need a “/heartbleed.txt” standard, and we need it ASAP by verandaguy on Wednesday April 09, 2014 @10:59AM (#7559676)
Interestingly enough, MtGox did this as well in the very early (pre-alpha) days of its role as a Bitcoin exchange.

Its developers were summarily bashed for this practice when seeking feedback (and rightly so).

Re:We need a “/heartbleed.txt” standard, and we need it ASAP by mschuster91 on Wednesday April 09, 2014 @10:37AM (#7559507)
...WHAT?! Did they use <form method="get"> for their login forms?
Re:We need a “/heartbleed.txt” standard, and we need it ASAP by _pmf_ on Wednesday April 09, 2014 @10:51AM (#7559615)
Relax. They have now switched to "post", and everything is just fine.
Re:We need a “/heartbleed.txt” standard, and we need it ASAP by mikeash on Wednesday April 09, 2014 @10:56AM (#7559659)
Is that really bigger? Heartbleed meant that I, sitting comfortably in my home, could hit up yahoo.com and grab your credentials without being anywhere near your computer, or any of the data your computer sends or receives.

Password in the URL with unencrypted HTTP is colossally dumb, but at least I have to either access your computer or at least snoop on its connection to take advantage of it.

Re:We need a “/heartbleed.txt” standard, and we need it ASAP by bitJericho on Wednesday April 09, 2014 @04:41PM (#7562211)
My point is that there have probably been hundreds of these types of events going back to the ancient times of the internet. The sky is not falling guys, just a good downpour.
Re:We need a “/heartbleed.txt” standard, and we need it ASAP by mikeash on Wednesday April 09, 2014 @04:50PM (#7562277)
My point is that heartbleed is unique in its combination of severity and scope. Something like 25% of all the web servers on the internet could have their most private data extracted for a period of two years. The sky isn't falling, but I can't think of anything else that comes close. Vulnerabilities that affect individual sites, while still really bad, still don't approach this.
Re:We need a “/heartbleed.txt” standard, and we need it ASAP by sixothree on Wednesday April 09, 2014 @11:21AM (#7559815)
Isn't Yahoo one (of the many) sites affected by heartbleed?
Re:We need a “/heartbleed.txt” standard, and we need it ASAP by mikeash on Wednesday April 09, 2014 @04:50PM (#7562281)
Yes, and they were particularly slow in patching it too. Took them over a day.