netdev - Re: [PATCH ipsec-next] xfrm: Allow xfrmi if

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20180723054615.jy3sxpzm2d6nqgga@gauss3.secunet.de>
Date:   Mon, 23 Jul 2018 07:46:15 +0200
From:   Steffen Klassert <steffen.klassert@...unet.com>
To:     Nathan Harold <nharold@...gle.com>
CC:     <netdev@...r.kernel.org>, <lorenzo@...gle.com>,
        <benedictwong@...gle.com>
Subject: Re: [PATCH ipsec-next] xfrm: Allow xfrmi if_id to be updated by UPDSA

On Thu, Jul 19, 2018 at 07:07:47PM -0700, Nathan Harold wrote:
> Allow attaching an SA to an xfrm interface id after
> the creation of the SA, so that tasks such as keying
> which must be done as the SA is created, can remain
> separate from the decision on how to route traffic
> from an SA. This permits SA creation to be decomposed
> in to three separate steps:
> 1) allocation of a SPI
> 2) algorithm and key negotiation
> 3) insertion into the data path
> 
> Signed-off-by: Nathan Harold <nharold@...gle.com>

Applied to ipsec-next, thanks Nathan!