Skip to content

25.3 FIPS - Using AES_128_GCM instead of AES_128_GCM_SIV#1471

Open
Enmk wants to merge 4 commits intoreleases/25.3.8-fipsfrom
fixes/25.3-fips/encryption_column_codecs
Open

25.3 FIPS - Using AES_128_GCM instead of AES_128_GCM_SIV#1471
Enmk wants to merge 4 commits intoreleases/25.3.8-fipsfrom
fixes/25.3-fips/encryption_column_codecs

Conversation

@Enmk
Copy link
Member

@Enmk Enmk commented Mar 3, 2026

Changelog category (leave one):

  • Improvement

Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):

Using AES_nnn_GCM instead of AES_nnn_GCM_SIV for column encryption codecs, since later is not FIPS-approved. Attempt to load AES_nnn_GCM_SIV-encrypted into FIPS build will fail early.

Documentation entry for user-facing changes

...

CI/CD Options

Exclude tests:

  • Fast test
  • Integration Tests
  • Stateless tests
  • Stateful tests
  • Performance tests
  • All with ASAN
  • All with TSAN
  • All with MSAN
  • All with UBSAN
  • All with Coverage
  • All with Aarch64
  • All Regression
  • Disable CI Cache

Regression jobs to run:

  • Fast suites (mostly <1h)
  • Aggregate Functions (2h)
  • Alter (1.5h)
  • Benchmark (30m)
  • ClickHouse Keeper (1h)
  • Iceberg (2h)
  • LDAP (1h)
  • Parquet (1.5h)
  • RBAC (1.5h)
  • SSL Server (1h)
  • S3 (2h)
  • Tiered Storage (2h)

Closes: #1450

Enmk added 2 commits March 3, 2026 15:51
Since later is not FIPS-approved
Also, AES_128_GCM has different codec byte to fail fast instead of
getting wrong data
@Enmk Enmk force-pushed the fixes/25.3-fips/encryption_column_codecs branch from 71fccc5 to 7cd50df Compare March 3, 2026 15:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant