Leo Famulari <l...@famulari.name> writes:

> Here are patches to replace openssl with openssl-1.0.2i and to update
> openssl-next to openssl@1.1.0a.
>
> From 1f020e2cb580941a36aa98737cd679a8605cdc4d Mon Sep 17 00:00:00 2001
> From: Leo Famulari <l...@famulari.name>
> Date: Thu, 22 Sep 2016 09:38:56 -0400
> Subject: [PATCH 1/2] gnu: openssl: Replace with 1.0.2i [security fixes].
>
> Fixes CVE-2016-{2177,2178,2179,2180,2181,2182,2183,6302,6303,6304,6306,6308}.
>
> * gnu/packages/tls.scm (openssl)[replacement]: New field.
> (openssl-1.0.2i): New variable.
> ---
>  gnu/packages/tls.scm | 19 +++++++++++++++++++
>  1 file changed, 19 insertions(+)
>
> diff --git a/gnu/packages/tls.scm b/gnu/packages/tls.scm
> index 0762703..198d298 100644
> --- a/gnu/packages/tls.scm
> +++ b/gnu/packages/tls.scm
> @@ -229,6 +229,7 @@ required structures.")
>  (define-public openssl
>    (package
>     (name "openssl")
> +   (replacement openssl-1.0.2i)
>     (version "1.0.2h")
>     (source (origin
>               (method url-fetch)
> @@ -367,6 +368,24 @@ required structures.")
>     (license license:openssl)
>     (home-page "http://www.openssl.org/";)))
>  
> +(define-public openssl-1.0.2i

Should this be kept private?  Otherwise, both patches look good to me,
please push.

     Thanks!
       Mark

Reply via email to