From: "Ludovic Courtès" <ludo@gnu.org>
To: Christopher Lemmer Webber <cwebber@dustycloud.org>
Cc: guix-devel@gnu.org
Subject: Re: Should we upgrade openssl?
Date: Tue, 16 Apr 2019 22:17:32 +0200 [thread overview]
Message-ID: <87r2a1d7s3.fsf@gnu.org> (raw)
In-Reply-To: <87wojvmk9n.fsf@dustycloud.org> (Christopher Lemmer Webber's message of "Mon, 15 Apr 2019 10:10:44 -0400")
Hello!
Christopher Lemmer Webber <cwebber@dustycloud.org> skribis:
> From the openssl website:
>
>> Note: The latest stable version is the 1.1.1 series. This is also our
>> Long Term Support (LTS) version, supported until 11th September
>> 2023. Our previous LTS version (1.0.2 series) will continue to be
>> supported until 31st December 2019 (security fixes only during the
>> last year of support). The 1.1.0 series is currently only receiving
>> security fixes and will go out of support on 11th September 2019. All
>> users of 1.0.2 and 1.1.0 are encouraged to upgrade to 1.1.1 as soon as
>> possible. The 0.9.8, 1.0.0 and 1.0.1 versions are now out of support
>> and should not be used.
>
> I know, everyone's going to groan hearing this, but maybe given the
> above it would make sense to upgrade to the openssl 1.1.0 series before
> Guix 1.0 gets out the door?
Indeed, I was under the assumption that 1.0 was still the stable
version, but apparently it’s not.
What do Leo and others think?
Thanks for the heads-up!
Ludo’.
next prev parent reply other threads:[~2019-04-16 20:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-15 14:10 Should we upgrade openssl? Christopher Lemmer Webber
2019-04-16 20:17 ` Ludovic Courtès [this message]
2019-04-17 6:09 ` Gábor Boskovits
2019-04-17 12:28 ` Ludovic Courtès
2019-04-17 12:31 ` Gábor Boskovits
2019-04-18 17:15 ` Ludovic Courtès
2019-04-19 16:56 ` Leo Famulari
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r2a1d7s3.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=cwebber@dustycloud.org \
--cc=guix-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).