From: Leo Famulari <leo@famulari.name>
To: guix-devel@gnu.org
Subject: Re: [PATCH 2/2] gnu: openssl-next: Update to 1.1.0d [fixes CVE-2017-{3730,3731,3732}].
Date: Thu, 26 Jan 2017 14:21:54 -0500 [thread overview]
Message-ID: <20170126192154.GA31485@jasmine> (raw)
In-Reply-To: <79693100b343086ccd4f3c05d273f10dc8595c84.1485458347.git.leo@famulari.name>
[-- Attachment #1: Type: text/plain, Size: 1211 bytes --]
On Thu, Jan 26, 2017 at 02:19:36PM -0500, Leo Famulari wrote:
> * gnu/packages/tls.scm (openssl-next): Update to 1.1.0d.
I forgot to sign this email.
> ---
> gnu/packages/tls.scm | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/gnu/packages/tls.scm b/gnu/packages/tls.scm
> index d2abf1223..5dac5dff5 100644
> --- a/gnu/packages/tls.scm
> +++ b/gnu/packages/tls.scm
> @@ -406,7 +406,7 @@ required structures.")
> (inherit openssl)
> (replacement #f)
> (name "openssl")
> - (version "1.1.0c")
> + (version "1.1.0d")
> (source (origin
> (method url-fetch)
> (uri (list (string-append "ftp://ftp.openssl.org/source/"
> @@ -417,7 +417,7 @@ required structures.")
> (patches (search-patches "openssl-1.1.0-c-rehash-in.patch"))
> (sha256
> (base32
> - "1xfn5ydl14myd9wgxm4nxy5a42cpp1g12ijf3g9m4mz0l90n8hzw"))))
> + "1pv0zql3r73qpjini90hn29l28d65b7i777zav0larbmi6gbnpkx"))))
> (outputs '("out"
> "doc" ;1.3MiB of man3 pages
> "static")) ; 5.5MiB of .a files
> --
> 2.11.0
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-01-26 19:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-26 19:19 [PATCH 0/2] OpenSSL security updates Leo Famulari
2017-01-26 19:19 ` [PATCH 1/2] gnu: openssl: Replace with openssl-1.0.2k [security fixes] Leo Famulari
2017-01-26 19:22 ` Leo Famulari
2017-01-26 19:19 ` [PATCH 2/2] gnu: openssl-next: Update to 1.1.0d [fixes CVE-2017-{3730, 3731, 3732}] Leo Famulari
2017-01-26 19:21 ` Leo Famulari [this message]
2017-01-26 21:43 ` [PATCH 0/2] OpenSSL security updates Marius Bakke
2017-01-26 23:53 ` 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=20170126192154.GA31485@jasmine \
--to=leo@famulari.name \
--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).