[FEATURE] Use fixed-work AES field transformations #3
Labels
No labels
alpha-1
bug
ci
docs
duplicate
enhancement
help wanted
invalid
performance
phase-6
question
refactor
security
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
erix/lib-aes#3
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem and motivation
Encrypted filesystem workloads need predictable byte-transform cost, including debug and test builds. Specify AES substitutions and field multiplication with work that is independent of the input byte values while preserving existing ciphertext and storage formats.
Proposed behavior and scope
Derive the byte transformations independently from FIPS 197. Use bounded algebraic substitutions and fixed-width field operations, without indexed secret-dependent tables. Preserve the current AES and XTS interfaces, key-schedule erasure and disk compatibility. Coordinate LibFsCrypto, E2fsd and the Integration source graph after the implementation is complete.
Authority, security and reliability
The arithmetic receives only its existing key, block and tweak buffers; it adds no I/O, allocation, dependency or capability. Preserve ownership and erasure of schedules and temporary buffers. Correctness and review of generated code take precedence over speed. Fixed source-level work is not a claim of universal machine-level constant time.
Acceptance criteria
Alternatives and tradeoffs
Tables can reduce arithmetic but introduce data-dependent memory accesses. Algebraic byte operations allow a direct derivation and a bounded operation sequence; compiler output still needs review on each supported target.
Tracking and rollout
Library audit, library PR, phase completion. Publish the reviewed library change first, then update its consumers and Integration catalogs together. No release or format migration is proposed.
The arithmetic change is published in
aed2eef2aa74114323e405a23b99513e723b4661, with matching LibFsCrypto, E2fsd and Integration selections. It preserves ciphertext and the existing interfaces. The selected x86-64 compiler output has also been reviewed; this does not establish constant time on every target.AES and LibFsCrypto pass their original push workflows. E2fsd now completes the formerly stalled crypto cases, but its workflow exposes a separate checker-image race. The final consumer criterion remains open until that workflow completes.
The fixed-work arithmetic is implemented and adopted by LibFsCrypto and E2fsd. The remaining consumer criterion is complete: E2fsd CI 415 passes its original encrypted workloads after the separate checker fixture repair. Integration selects the repaired consumer. Closing this implementation issue; the broader library audit remains open.