From: Ralf <ralf+gentoo@ramses-pyramidenbau.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: 'Heartbleed' bug
Date: Fri, 11 Apr 2014 01:42:34 +0200 [thread overview]
Message-ID: <53472C6A.2050209@ramses-pyramidenbau.de> (raw)
In-Reply-To: <li77hc$fko$1@ger.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 879 bytes --]
Hi,
On 04/11/2014 12:55 AM, walt wrote:
> Steve Gibson explained that the heartbeat feature was introduced in openssl to
> allow *UDP* connections to mimic the 'keepalive' function of the TCP protocol.
>
> IIRC Steve didn't explain how UDP bugs can compromise TCP connections.
>
> Anyone here really understand the underlying principles? If so, please explain!
yes, a TCP connection is stateful, so imho heartbeat is not necessary.
But you don't always speak "UDP" or "TCP".
Imagine some sort of direct connection without any type of
transportation layer.
As a generic cryptographic library, OpenSSL is designed to be adaptable
and universal. That broke OpenSSL's neck.
We only can hope, that the heartbeat exploit was not widely used before
they published that zero-day.
But we can be sure, that this is not going to be the last vulnerability
of this kind.
Regards
Ralf
[-- Attachment #2: Type: text/html, Size: 1416 bytes --]
next prev parent reply other threads:[~2014-04-10 23:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-10 0:06 [gentoo-user] 'Heartbleed' bug Joseph
2014-04-10 0:13 ` Ralf
2014-04-10 0:32 ` Michael Orlitzky
2014-04-10 5:48 ` Pavel Volkov
2014-04-10 9:03 ` Adam Carter
2014-04-10 9:53 ` Ján Zahornadský
2014-04-10 10:52 ` Matthew Finkel
2014-04-10 10:51 ` Nilesh Govindrajan
2014-04-10 11:00 ` Randolph Maaßen
2014-04-10 11:06 ` Ján Zahornadský
2014-04-10 11:06 ` Neil Bothwick
2014-04-10 10:42 ` Marc Joliet
2014-04-10 22:55 ` [gentoo-user] " walt
2014-04-10 22:59 ` Alan McKinnon
2014-04-10 23:38 ` Chris Walters
2014-04-10 23:37 ` Matthew Finkel
2014-04-10 23:42 ` Ralf [this message]
2014-04-11 8:05 ` Philip Webb
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53472C6A.2050209@ramses-pyramidenbau.de \
--to=ralf+gentoo@ramses-pyramidenbau.de \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox