summaryrefslogtreecommitdiffstats
path: root/src/plugins/dma_intel
diff options
context:
space:
mode:
authorMatthew Smith <mgsmith@netgate.com>2024-02-12 18:39:21 +0000
committerFan Zhang <fanzhang.oss@gmail.com>2024-02-19 15:35:54 +0000
commitff71939c30ae81241808da1843e82cf2dfa92344 (patch)
treed9bd6831058757436b51e87356c91951f592cb65 /src/plugins/dma_intel
parent37127f7bcc468ebe68936362c2a4e086b25bf202 (diff)
ipsec: check each packet for no algs in esp-encrypt
In esp_encrypt_inline(), if two or more consecutive packets are associated with the same SA which has no crypto or integrity algorithms set, only the first one gets dropped. Subsequent packets either get sent (synchronous crypto) or cause a segv (asynchronous crypto). The current SA's index and pool entry are cached before it can be determined whether the packet should be dropped due to no algorithms being set. The check for no algorithms is only performed when the cached SA index is different than the SA index for the current packet. So packets after the first one associated with the "none" alg SA aren't handled properly. This was broken by my previous commit ("ipsec: keep esp encrypt pointer and index synced") which fixed a segv that occurred under a different set of circumstances. Check whether each packet should be dropped instead of only checking when a new SA is encountered. Update unit tests: - Add a test for no algs on tunnel interface which enables asynchronous crypto. - Send more than one packet in the tests for no algs. Type: fix Fixes: dac9e566cd16fc375fff14280b37cb5135584fc6 Signed-off-by: Matthew Smith <mgsmith@netgate.com> Change-Id: I69e951f22044051eb8557da187cb58f5535b54bf
Diffstat (limited to 'src/plugins/dma_intel')
0 files changed, 0 insertions, 0 deletions