From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: [RFC] LibreSSL, introduce virtual/openssl
Date: Wed, 16 Jul 2014 07:16:33 +0000 (UTC) [thread overview]
Message-ID: <pan$e289a$570ad7eb$265fb3d9$c86a51ec@cox.net> (raw)
In-Reply-To: CAET+hMRirmGh+QkeYSKTJMFU4GDv5BULm1rNmEp=4xbxDXPE3A@mail.gmail.com
Matthew Summers posted on Tue, 15 Jul 2014 09:18:23 -0500 as excerpted:
> So, libressl is really nowhere near ready for prime time or even late
> night TV (perhaps the day time talk shows, but that is a stretch given
> the PRNG situation). I think preparing a virtual and updating dependent
> ebuilds for the explosion of replacements is grand, however we should
> make it _very_ clear to everyone that issues exist that make libressl
> unsafe for anything other than play time.
Here's another link for those following along:
Ars-technica (via LWN):
OpenSSL fork LibreSSL is declared "unsafe for Linux"
http://lwn.net/Articles/605509/rss
Basically it's a pid-duplication issue, aka an "I'm my own grandpa"
issue, as someone mentions in the comments.
There's also a note both in the comments and now on the original Ars
article saying a patch has already been pushed, but the point stands,
"nowhere near ready for prime time" indeed.
It'll take a bit of time, but for now as already suggested, introducing
the virtual with the single openssl provider does seem reasonable.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2014-07-16 7:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-12 12:37 [gentoo-dev] [RFC] LibreSSL, introduce virtual/openssl hasufell
2014-07-12 14:28 ` Anthony G. Basile
2014-07-12 14:35 ` hasufell
2014-07-12 15:42 ` William Hubbs
2014-07-12 18:51 ` Dirkjan Ochtman
2014-07-13 17:59 ` hasufell
2014-07-15 14:18 ` Matthew Summers
2014-07-15 14:47 ` hasufell
2014-07-16 7:16 ` Duncan [this message]
2015-01-23 1:51 ` hasufell
2015-01-23 5:56 ` Michał Górny
2015-01-23 9:05 ` Diego Elio Pettenò
2015-01-23 13:25 ` Anthony G. Basile
2015-01-23 20:18 ` hasufell
2015-01-23 22:37 ` Rich Freeman
2015-01-26 10:43 ` Peter Stuge
2015-01-26 12:08 ` Rich Freeman
2015-01-26 16:01 ` Peter Stuge
2015-01-26 17:55 ` Rich Freeman
2015-01-27 0:54 ` hasufell
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='pan$e289a$570ad7eb$265fb3d9$c86a51ec@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=gentoo-dev@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