mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] strongswan: update to 5.0.4
Date: Mon, 13 May 2013 09:32:33 +0200	[thread overview]
Message-ID: <20130513073233.GC23679@pengutronix.de> (raw)
In-Reply-To: <1367503277-12005-1-git-send-email-jlu@pengutronix.de>

On Thu, May 02, 2013 at 04:01:17PM +0200, Jan Luebbe wrote:
> The security bug fixed in 5.0.4 affected only the openssl plugin,
> which is disabled in this package.

Thanks, applied.

Michael

> ---
>  rules/strongswan.make |   13 ++++++++++---
>  1 file changed, 10 insertions(+), 3 deletions(-)
> 
> diff --git a/rules/strongswan.make b/rules/strongswan.make
> index 31b7221..6401832 100644
> --- a/rules/strongswan.make
> +++ b/rules/strongswan.make
> @@ -17,8 +17,8 @@ PACKAGES-$(PTXCONF_STRONGSWAN) += strongswan
>  #
>  # Paths and names
>  #
> -STRONGSWAN_VERSION	:= 5.0.2
> -STRONGSWAN_MD5		:= 77dc16443fd141f46183d3a4f60986ef
> +STRONGSWAN_VERSION	:= 5.0.4
> +STRONGSWAN_MD5		:= 0ab0397b44b197febfd0f89148344035
>  STRONGSWAN		:= strongswan-$(STRONGSWAN_VERSION)
>  STRONGSWAN_SUFFIX	:= tar.bz2
>  STRONGSWAN_URL		:= http://download.strongswan.org/$(STRONGSWAN).$(STRONGSWAN_SUFFIX)
> @@ -34,6 +34,7 @@ STRONGSWAN_CONF_TOOL	:= autoconf
>  STRONGSWAN_CONF_OPT	:= \
>  	$(CROSS_AUTOCONF_USR) \
>  	--$(call ptx/endis, PTXCONF_STRONGSWAN_LIBCURL)-curl \
> +	--disable-unbound \
>  	--disable-soup \
>  	--disable-ldap \
>  	--enable-aes \
> @@ -57,6 +58,7 @@ STRONGSWAN_CONF_OPT	:= \
>  	--enable-pkcs8 \
>  	--enable-pgp \
>  	--enable-dnskey \
> +	--disable-ipseckey \
>  	--enable-pem \
>  	--enable-hmac \
>  	--enable-cmac \
> @@ -95,6 +97,7 @@ STRONGSWAN_CONF_OPT	:= \
>  	--enable-xauth-generic \
>  	--disable-xauth-eap \
>  	--disable-xauth-pam \
> +	--disable-xauth-noauth \
>  	--disable-tnc-ifmap \
>  	--disable-tnc-pdp \
>  	--disable-tnc-imc \
> @@ -146,7 +149,7 @@ STRONGSWAN_CONF_OPT	:= \
>  	--disable-addrblock \
>  	--disable-unity \
>  	--disable-uci \
> -	--disable-android \
> +	--disable-android-dns \
>  	--disable-android-log \
>  	--disable-maemo \
>  	--disable-nm \
> @@ -155,6 +158,7 @@ STRONGSWAN_CONF_OPT	:= \
>  	--disable-lookip \
>  	--disable-error-notify \
>  	--disable-certexpire \
> +	--disable-systime-fix \
>  	--disable-led \
>  	--disable-duplicheck \
>  	--disable-coupling \
> @@ -162,6 +166,9 @@ STRONGSWAN_CONF_OPT	:= \
>  	--disable-vstr \
>  	--disable-monolithic \
>  	--disable-bfd-backtraces \
> +	--disable-unit-tests \
> +	--disable-tkm \
> +	--disable-defaults \
>  	--enable-dependency-tracking \
>  	--enable-shared \
>  	--disable-static \
> -- 
> 1.7.10.4
> 
> 
> -- 
> ptxdist mailing list
> ptxdist@pengutronix.de
> 

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

-- 
ptxdist mailing list
ptxdist@pengutronix.de

      reply	other threads:[~2013-05-13  7:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-02 14:01 Jan Luebbe
2013-05-13  7:32 ` Michael Olbrich [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=20130513073233.GC23679@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /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