From: Stephen Hemminger <stephen@networkplumber.org>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] CVE-2014-0160 : heartbleed CVE on openssl - http://heartbleed.com/
Date: Tue, 8 Apr 2014 10:01:40 -0700 [thread overview]
Message-ID: <20140408100140.0245fed5@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <CAA93jw7aJ0jEgMwSEuS+YddRCW32=-4dzUiZrNcOGW12m_hWAQ@mail.gmail.com>
On Mon, 7 Apr 2014 18:38:58 -0700
Dave Taht <dave.taht@gmail.com> wrote:
> This one looks pretty nasty.
>
> see http://lwn.net/Articles/593683/ for more details.
>
> The headache and cost of updating all the gear I maintain is insanely high.
>
> Some of my OSes are so old as to no longer have updates, others have ssl certs
> that I can now no longer trust for email or imap, still others work on
> the vpn... and I only have a few dozen machines to fix, personally.
Actually, not as bad as it looks. The old OS's did not get more recent
versions of OpenSSL which have the bug. So in this case lazy vendors win out.
From heartbleed.com:
Some operating system distributions that have shipped with potentially vulnerable OpenSSL version:
Debian Wheezy (stable), OpenSSL 1.0.1e-2+deb7u4
Ubuntu 12.04.4 LTS, OpenSSL 1.0.1-4ubuntu5.11
CentOS 6.5, OpenSSL 1.0.1e-15
Fedora 18, OpenSSL 1.0.1e-4
OpenBSD 5.3 (OpenSSL 1.0.1c 10 May 2012) and 5.4 (OpenSSL 1.0.1c 10 May 2012)
FreeBSD 10.0 - OpenSSL 1.0.1e 11 Feb 2013
NetBSD 5.0.2 (OpenSSL 1.0.1e)
OpenSUSE 12.2 (OpenSSL 1.0.1c)
Operating system distribution with versions that are not vulnerable:
Debian Squeeze (oldstable), OpenSSL 0.9.8o-4squeeze14
SUSE Linux Enterprise Server
FreeBSD 8.4 - OpenSSL 0.9.8y 5 Feb 2013
FreeBSD 9.2 - OpenSSL 0.9.8y 5 Feb 2013
FreeBSD Ports - OpenSSL 1.0.1g (At 7 Apr 21:46:40 2014 UTC)
prev parent reply other threads:[~2014-04-08 17:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-08 1:38 Dave Taht
2014-04-08 17:01 ` Stephen Hemminger [this message]
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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140408100140.0245fed5@nehalam.linuxnetplumber.net \
--to=stephen@networkplumber.org \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/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