From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] strongSwan: update to 5.8.2
Date: Thu, 20 Feb 2020 13:57:39 +0000 [thread overview]
Message-ID: <0C63ED86-A3D8-4CB3-8AFC-C5C776755397@ipfire.org> (raw)
In-Reply-To: <364aa4eb-6f7f-3145-b265-83e5e43741f3@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 3141 bytes --]
Acked-by: Michael Tremer <michael.tremer(a)ipfire.org>
> On 19 Feb 2020, at 21:48, Peter Müller <peter.mueller(a)ipfire.org> wrote:
>
> Please refer to https://wiki.strongswan.org/versions/75 for release notes.
>
> Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
> ---
> config/rootfiles/common/strongswan | 3 +++
> lfs/strongswan | 6 +++---
> 2 files changed, 6 insertions(+), 3 deletions(-)
>
> diff --git a/config/rootfiles/common/strongswan b/config/rootfiles/common/strongswan
> index cc6a59e7f..d337ef506 100644
> --- a/config/rootfiles/common/strongswan
> +++ b/config/rootfiles/common/strongswan
> @@ -27,6 +27,7 @@ etc/strongswan.d/charon/curve25519.conf
> etc/strongswan.d/charon/des.conf
> etc/strongswan.d/charon/dhcp.conf
> etc/strongswan.d/charon/dnskey.conf
> +etc/strongswan.d/charon/drbg.conf
> etc/strongswan.d/charon/eap-identity.conf
> etc/strongswan.d/charon/eap-mschapv2.conf
> etc/strongswan.d/charon/eap-peap.conf
> @@ -122,6 +123,7 @@ usr/lib/ipsec/plugins/libstrongswan-curve25519.so
> usr/lib/ipsec/plugins/libstrongswan-des.so
> usr/lib/ipsec/plugins/libstrongswan-dhcp.so
> usr/lib/ipsec/plugins/libstrongswan-dnskey.so
> +usr/lib/ipsec/plugins/libstrongswan-drbg.so
> usr/lib/ipsec/plugins/libstrongswan-eap-identity.so
> usr/lib/ipsec/plugins/libstrongswan-eap-mschapv2.so
> usr/lib/ipsec/plugins/libstrongswan-eap-peap.so
> @@ -208,6 +210,7 @@ usr/sbin/swanctl
> #usr/share/strongswan/templates/config/plugins/des.conf
> #usr/share/strongswan/templates/config/plugins/dhcp.conf
> #usr/share/strongswan/templates/config/plugins/dnskey.conf
> +#usr/share/strongswan/templates/config/plugins/drbg.conf
> #usr/share/strongswan/templates/config/plugins/eap-identity.conf
> #usr/share/strongswan/templates/config/plugins/eap-mschapv2.conf
> #usr/share/strongswan/templates/config/plugins/eap-peap.conf
> diff --git a/lfs/strongswan b/lfs/strongswan
> index c6f428e41..ed88c0458 100644
> --- a/lfs/strongswan
> +++ b/lfs/strongswan
> @@ -1,7 +1,7 @@
> ###############################################################################
> # #
> # IPFire.org - A linux based firewall #
> -# Copyright (C) 2007-2018 IPFire Team <info(a)ipfire.org> #
> +# Copyright (C) 2007-2020 IPFire Team <info(a)ipfire.org> #
> # #
> # This program is free software: you can redistribute it and/or modify #
> # it under the terms of the GNU General Public License as published by #
> @@ -24,7 +24,7 @@
>
> include Config
>
> -VER = 5.8.1
> +VER = 5.8.2
>
> THISAPP = strongswan-$(VER)
> DL_FILE = $(THISAPP).tar.bz2
> @@ -40,7 +40,7 @@ objects = $(DL_FILE)
>
> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>
> -$(DL_FILE)_MD5 = 5a6b9980cd1ac4fad3c24b55ed960ac9
> +$(DL_FILE)_MD5 = d94eac2caed51b0cc776e5887b10bace
>
> install : $(TARGET)
>
> --
> 2.16.4
>
prev parent reply other threads:[~2020-02-20 13:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 21:48 Peter Müller
2020-02-20 13:57 ` Michael Tremer [this message]
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=0C63ED86-A3D8-4CB3-8AFC-C5C776755397@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.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