On Mon, Jun 22, 2015 at 1:44 AM, Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> wrote:
>
> Here is the crypto update for 4.2:
So this generates conflicts with your earlier changes (that I got
through the networking tree - they are your patches, but they went
through Steffen Klassert and then David Miller).
I resolved them, but I want you to double-check the end result.
Some of the conflicts are just trivial (but annoying) conflicts due to
whitespace changes to the vmx routines.
But the changes to net/ipv4/esp4.c and net/ipv6/esp6.c are actual real
code conflicts, even though the in the merge they look like no change
at all, because I picked your side and the changes on the other side
just went away.
I did that, because ss far as I can tell, the changes in commits
7021b2e1cddd and 000ae7b2690e (that switch esp4/6 over to the new AEAD
interface) obviate the commits I got earlier to use the high-order
sequence number bits for IV generation.
So it looks to me like those AEAD interface changes already make sure
to use the full 64 bits of the sequence number.
But if I'm wrong, please holler. You clearly know both sides of this,
since you wrote all the patches involved, so I'd like you to
double-check me.
Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-crypto" in
