aboutsummaryrefslogtreecommitdiffstats
path: root/extras/strongswan/vpp_sswan/Makefile
diff options
context:
space:
mode:
authorMatthew Smith <mgsmith@netgate.com>2024-02-12 18:39:21 +0000
committerAndrew Yourtchenko <ayourtch@gmail.com>2024-03-11 20:18:42 +0000
commita541cfd31dca351a736362b4e06b626236f340dd (patch)
tree8ce385d620d960a1a2e5b97a71da4d1c6ee94680 /extras/strongswan/vpp_sswan/Makefile
parent1200c799d0b346f28deb76daa8f643e771976da7 (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 (cherry picked from commit ff71939c30ae81241808da1843e82cf2dfa92344)
Diffstat (limited to 'extras/strongswan/vpp_sswan/Makefile')
0 files changed, 0 insertions, 0 deletions