From: ludo@gnu.org (Ludovic Courtès)
To: Leo Famulari <leo@famulari.name>
Cc: 30966@debbugs.gnu.org
Subject: [bug#30966] [PATCH] gnu: openssl: Replace with OpenSSL 1.0.2o [fixes CVE-2018-0739].
Date: Wed, 28 Mar 2018 17:05:37 +0200 [thread overview]
Message-ID: <87efk4tf3y.fsf@gnu.org> (raw)
In-Reply-To: <97a98c7fe0dfe6f98839e9cabf8e0022d7d2a8c8.1522190671.git.leo@famulari.name> (Leo Famulari's message of "Tue, 27 Mar 2018 18:44:31 -0400")
Hi Leo,
Leo Famulari <leo@famulari.name> skribis:
> * gnu/packages/tls.scm (openssl)[replacement]: New field.
> (openssl-1.0.2o): New variable.
[...]
> + (uri (list (string-append "https://www.openssl.org/source/openssl-"
> + version ".tar.gz")
> + (string-append "ftp://ftp.openssl.org/source/"
> + name "-" version ".tar.gz")
> + (string-append "ftp://ftp.openssl.org/source/old/"
> + (string-trim-right version char-set:letter)
> + "/" name "-" version ".tar.gz")))
Eventually we should factorize this in an ‘openssl-source-url’ procedure.
> + (sha256
> + (base32
> + "0kcy13l701054nhpbd901mz32v1kn4g311z0nifd83xs2jbmqgzc"))
> + ;; Erase the inherited snippet, which isn't applicable to
> + ;; OpenSSL 1.0.2o.
> + (snippet
> + '(begin
> + #t))))))
Use (snippet #f) to really annihilate the snippet, otherwise you create
a snippet that does nothing, yet entails and unpack-and-repack step.
OK with this change, thank you!
Ludo’.
next prev parent reply other threads:[~2018-03-28 15:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-27 22:44 [bug#30966] [PATCH] gnu: openssl: Replace with OpenSSL 1.0.2o [fixes CVE-2018-0739] Leo Famulari
2018-03-28 15:05 ` Ludovic Courtès [this message]
2018-03-28 18:11 ` bug#30966: " 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87efk4tf3y.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=30966@debbugs.gnu.org \
--cc=leo@famulari.name \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.