From: Michael Orlitzky <mjo@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] 'Heartbleed' bug
Date: Wed, 09 Apr 2014 20:32:34 -0400 [thread overview]
Message-ID: <5345E6A2.2030400@gentoo.org> (raw)
In-Reply-To: <20140410000635.GB9729@syscon7.ed.shawcable.net>
On 04/09/2014 08:06 PM, Joseph wrote:
> Is gentoo effected by this new 'Heartbleed' bug?
>
> "The Heartbleed Bug is a serious vulnerability in the popular OpenSSL
> cryptographic software library...."
>
> http://heartbleed.com/
>
Yes, upgrade your OpenSSL to the latest stable version, and if 1.0.1g
isn't stable on your arch (it should be unless it's a weird one), unset
USE=tls-heartbeat like Ralf said.
But that's not your big problem. If you operate any servers, the private
keys to any OpenSSL-backed service may have been compromised. So the old
certificates all need to be revoked and new ones issued. That includes
Apache, OpenVPN, Postfix, Dovecot -- all the big ones. Even if you don't
run servers, other people do, and they were probably vulnerable. So any
passwords you've used on the web in the past two years should be changed.
next prev parent reply other threads:[~2014-04-10 0:32 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 [this message]
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
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=5345E6A2.2030400@gentoo.org \
--to=mjo@gentoo.org \
--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