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)
Fri, Mar 7, 7:36 PM
Unknown Object (File)
Mon, Mar 3, 2:35 AM
Unknown Object (File)
Feb 16 2025, 11:31 PM
Unknown Object (File)
Feb 8 2025, 5:13 AM
Unknown Object (File)
Feb 5 2025, 12:32 AM
Unknown Object (File)
Jan 18 2025, 12:23 AM
Unknown Object (File)
Dec 21 2024, 4:22 PM
Unknown Object (File)
Dec 9 2024, 5:28 PM
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