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.
My upgraded debian and ubuntu boxes are still reported as vulnerable.... Who's wrong, who's right?
Have you restarted the services linked against openssl?
lsof | grep ssl | grep DEL
It was indeed the restart step that was missing
Would love to see the code and test it against a rebuilt a patched nginx.
Filippo has hosted it with github.
Re:The Heartbleed Bug
by danielhlockard on Monday April 07, 2014 @11:34PM
(#7551303)
Just run it against it?
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
Exactly what I was looking for, thanks! This should be part of the official heartbleed site not hidden away in comments here.
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.