netdev - Re: [PATCH net-next 0/2] Removal of struct esp

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20131029121105.GF31491@secunet.com>
Date:	Tue, 29 Oct 2013 13:11:05 +0100
From:	Steffen Klassert <steffen.klassert@...unet.com>
To:	David Miller <davem@...emloft.net>
Cc:	mathias.krause@...unet.com, netdev@...r.kernel.org,
	herbert@...dor.apana.org.au
Subject: Re: [PATCH net-next 0/2] Removal of struct esp_data

On Wed, Oct 23, 2013 at 03:40:02PM -0400, David Miller wrote:
> From: Steffen Klassert <steffen.klassert@...unet.com>
> Date: Wed, 23 Oct 2013 10:07:16 +0200
> 
> > Well, I thought to either take this as a reminder to implement the
> > missing stuff or to take the removing patches if this is really obsolete.
> > I'll do one of both once I'm back from conference week in Edinburgh.
> 
> Sounds like a good plan, thanks.

RFC 4303 recommends to use TFC padding instead of the padding field:

'As noted above, the Padding field is limited to 255 bytes in length.
This generally will not be adequate to hide traffic characteristics
relative to traffic flow confidentiality requirements.  An optional
field, within the payload data, is provided specifically to address
the TFC requirement.'

So looks like we can remove the padlen field, both patches
applied to ipsec-next. Thanks Mathias!
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html