lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 25 Apr 2014 15:22:30 -0400
From: Bennett Todd <>
To: Dillon Korman <>
Subject: Re: [FD] Legitimacy of new Heartbleed exploit?

On Fri, Apr 25, 2014 at 2:18 PM, Dillon Korman <> wrote:
> Saw a link to this:


> There is no actual exploit code in there since they insist of keeping it

It'd be a lot less funny if they didn't keep it private. They claim to have
found a buffer overflow in the handling of the DOPENSSL_NO_HEARTBEATS
variable; since that's in the C Preprocessor, that's a rather extraordinary

> Do you think there really is a working exploit on new versions of OpenSSL?

Absolutely! Ask again in a year; if, say, Theo's LibreTLS "flensing" has
gotten to fly, and the Linux Foundation's attempt to fund maintenance of
critical infrastructure has had a little time to work.

But the TLS protocol itself, which must be replaced in every browser, is
designed first and foremost to guarantee that no-one can publish content
securely unless they've paid a tithe to a certificate authority; presumably
someone, somewhere, confused "enriching numbers salesmen" with "improving
security. The fiscal security of Verisign and their friends is covered, the
rest of us need a different protocol.

Sent through the Full Disclosure mailing list
Web Archives & RSS:

Powered by blists - more mailing lists