Page MenuHomeFreeBSD

Fix AES-CTR compatibility issue in ipsec
ClosedPublic

Authored by kd on May 25 2020, 11:00 AM.
Tags
None
Referenced Files
Unknown Object (File)
Tue, Oct 29, 11:37 PM
Unknown Object (File)
Oct 5 2024, 7:08 AM
Unknown Object (File)
Sep 8 2024, 6:53 AM
Unknown Object (File)
Sep 7 2024, 8:54 AM
Unknown Object (File)
Sep 7 2024, 7:00 AM
Unknown Object (File)
Sep 5 2024, 5:34 PM
Unknown Object (File)
Sep 2 2024, 12:56 AM
Unknown Object (File)
Aug 23 2024, 6:57 AM
Subscribers

Details

Summary

r361390 decreased blocksize of AES-CTR from 16 to 1. Because of that ESP payload is no longer aligned to 16 bytes before being encrypted and sent.
This is a good change since RFC3686 specifies that the last block doesn't need to be aligned.
Because FreeBSD before r361390 couldn't decrypt partial blocks encrypted with AES-CTR we need to enforce 16 byte alignment in order to preserve compatibility.
Add a sysctl(on by default) to control it.

Test Plan

Create ipsec tunnel with FreeBSD host without r361390 and use AES-CTR encryption.
Ping it, turn the sysctl off, try to ping it again and verify that connectivity was lost.
Do a similar test connecting to a Linux host and FreeBSD with this patch applied.

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Skipped
Unit
Tests Skipped