News for hackers. Stuff that matters.
Re:The Heartbleed Bug by FiloSottile on Monday April 07, 2014 @09:02PM (#7550793)
I've built a web tester for this bug, find it at

http://filippo.io/Heartbleed/

It actually exploit the bug, since it was quite trivial, and echo some memory.

It's written in Go, no more than 100 lines. I'll release code in some time.

Re:The Heartbleed Bug by leocassarani on Tuesday April 08, 2014 @06:21AM (#7552473)
Interestingly, your tool claims our website (SSL-terminated at our ELB instance) is still vulnerable; while this other tool (http://possible.lv/tools/hb) claims we are unaffected.

Another, known unpatched, app is reported to be affected by both tools.

Is it possible that FiloSottile/Hearbleed may report false positives?

Re:The Heartbleed Bug by danielweber on Tuesday April 08, 2014 @01:04PM (#7554648)
From what I've learned, it reports back if it gets something, when it should get nothing.

How vulnerable a specific site is depends on luck. Yahoo must have broken a whole bunch of mirrors because total amateurs can send mail.yahoo.com a certain blob of code and it has a good chance of returning a stranger's password.

Re:The Heartbleed Bug by raphinou on Tuesday April 08, 2014 @05:21AM (#7552290)
My upgraded debian and ubuntu boxes are still reported as vulnerable.... Who's wrong, who's right?
Re:The Heartbleed Bug by ch0wn on Tuesday April 08, 2014 @05:54AM (#7552393)
Have you restarted the services linked against openssl?

lsof | grep ssl | grep DEL

Re:The Heartbleed Bug by raphinou on Tuesday April 08, 2014 @08:30AM (#7552919)
It was indeed the restart step that was missing
Re:The Heartbleed Bug by chirayuk on Monday April 07, 2014 @11:27PM (#7551282)
Would love to see the code and test it against a rebuilt a patched nginx.
Re:The Heartbleed Bug by somuser01 on Tuesday April 08, 2014 @07:08AM (#7552610)
Filippo has hosted it with github.

https://github.com/FiloSottile/Heartbleed

Re:The Heartbleed Bug by danielhlockard on Monday April 07, 2014 @11:34PM (#7551303)
Just run it against it?
Re:The Heartbleed Bug by chirayuk on Tuesday April 08, 2014 @02:10AM (#7551668)
Well, I was interested in actually testing it out in code. I got it working with the pyOpenSSL bindings (I had to expose struct ssl_method_st, SSL_get_ssl_method, ssl_write_bytes and rebuild cryptography for pyOpenSSL.) Fun times.
Re:The Heartbleed Bug by edwintorok on Tuesday April 08, 2014 @03:52AM (#7552010)
It says that the heartbleed.com site itself is vulnerable.
Re:The Heartbleed Bug by edwintorok on Tuesday April 08, 2014 @07:19AM (#7552661)
Looks like its fixed
Re:The Heartbleed Bug by dewey on Tuesday April 08, 2014 @06:38AM (#7552526)
Exactly what I was looking for, thanks! This should be part of the official heartbleed site not hidden away in comments here.
Re:The Heartbleed Bug by endeavour on Monday April 07, 2014 @10:40PM (#7551148)
Nice work