aboutsummaryrefslogtreecommitdiffstats
path: root/net/xfrm/xfrm_algo.c
diff options
context:
space:
mode:
authorSteffen Klassert <steffen.klassert@secunet.com>2011-05-09 19:43:05 +0000
committerDavid S. Miller <davem@davemloft.net>2011-05-10 15:03:34 -0700
commit6fa5ddcc675b937f94d05628e8997c07a80c6cb9 (patch)
tree22d71ef353fe4e2f94a5c83e9b15e7bfa420e5df /net/xfrm/xfrm_algo.c
parent43a4dea4c9d44baae38ddc14b9b6d86fde4c8b88 (diff)
downloadkernel_samsung_aries-6fa5ddcc675b937f94d05628e8997c07a80c6cb9.zip
kernel_samsung_aries-6fa5ddcc675b937f94d05628e8997c07a80c6cb9.tar.gz
kernel_samsung_aries-6fa5ddcc675b937f94d05628e8997c07a80c6cb9.tar.bz2
xfrm: Don't allow esn with disabled anti replay detection
Unlike the standard case, disabled anti replay detection needs some nontrivial extra treatment on ESN. RFC 4303 states: Note: If a receiver chooses to not enable anti-replay for an SA, then the receiver SHOULD NOT negotiate ESN in an SA management protocol. Use of ESN creates a need for the receiver to manage the anti-replay window (in order to determine the correct value for the high-order bits of the ESN, which are employed in the ICV computation), which is generally contrary to the notion of disabling anti-replay for an SA. So return an error if an ESN state with disabled anti replay detection is inserted for now and add the extra treatment later if we need it. Signed-off-by: Steffen Klassert <steffen.klassert@secunet.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/xfrm/xfrm_algo.c')
0 files changed, 0 insertions, 0 deletions