public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] strongswan: Update to version 5.9.10
Date: Mon, 06 Mar 2023 16:42:13 +0000	[thread overview]
Message-ID: <ff5237de-cd45-b54f-db78-de38baf218f7@ipfire.org> (raw)
In-Reply-To: <20230306153355.3445300-1-adolf.belka@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 2740 bytes --]

As always, thank you very much! :-)

Reviewed-by: Peter Müller <peter.mueller(a)ipfire.org>

> - Update from version 5.9.9 to 5.9.10
> - Update of rootfile not required
> - Changelog
> strongswan-5.9.10
> - Fixed a vulnerability related to certificate verification in TLS-based EAP
>   methods that leads to an authentication bypass followed by an expired pointer
>   dereference that results in a denial of service and possibly even remote code
>   execution.
>   This vulnerability has been registered as CVE-2023-26463.
> - Added support for full packet hardware offload for IPsec SAs and policies with
>   Linux 6.2 kernels to the kernel-netlink plugin.
> - TLS-based EAP methods now use the standardized key derivation when used
>   with TLS 1.3.
> - The eap-tls plugin properly supports TLS 1.3 according to RFC 9190, by
>   implementing the "protected success indication".
> - With the `prefer` value for the `childless` setting, initiators will create
>   a childless IKE_SA if the responder supports the extension.
> - Routes via XFRM interfaces can optionally be installed automatically by
>   enabling the `install_routes_xfrmi` option of the kernel-netlink plugin.
> - charon-nm now uses XFRM interfaces instead of dummy TUN devices to avoid
>   issues with name resolution if they are supported by the kernel.
> - The `pki --req` command can encode extendedKeyUsage (EKU) flags in the
>   PKCS#10 certificate signing request.
> - The `pki --issue` command adopts EKU flags from CSRs but allows modifying them
>   (replace them completely, or adding/removing specific flags).
> - On Linux 6.2 kernels, the last use times of CHILD_SAs are determined via the
>   IPsec SAs instead of the policies.
> - For libcurl with MultiSSL support, the curl plugin provides an option to
>   select the SSL/TLS backend.
> 
> Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
> ---
>  lfs/strongswan | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/lfs/strongswan b/lfs/strongswan
> index db4607bc2..7cb886fe7 100644
> --- a/lfs/strongswan
> +++ b/lfs/strongswan
> @@ -24,7 +24,7 @@
>  
>  include Config
>  
> -VER        = 5.9.9
> +VER        = 5.9.10
>  
>  THISAPP    = strongswan-$(VER)
>  DL_FILE    = $(THISAPP).tar.bz2
> @@ -40,7 +40,7 @@ objects = $(DL_FILE)
>  
>  $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>  
> -$(DL_FILE)_BLAKE2 = 9cbc73192527254a2d20b28295e7583a0d9ec81e4d6eb1b7d78e54b30ba8e5304a33e813145d8a47b2b4319d7b49762cd35cdbdaf1d41161d7746d68d3cef1b5
> +$(DL_FILE)_BLAKE2 = 757d55aa0c623356c5d8bf0360df63990ec18294d06f50b6dd475273b75a883354ea8723708e4856a8f0acc4d3237ac6bcf5adc40346fded7051d78375b2bcc9
>  
>  install : $(TARGET)
>  

      reply	other threads:[~2023-03-06 16:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-06 15:33 Adolf Belka
2023-03-06 16:42 ` Peter Müller [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=ff5237de-cd45-b54f-db78-de38baf218f7@ipfire.org \
    --to=peter.mueller@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