Use fixed AES field transformations #7
No reviewers
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!7
Loading…
Reference in a new issue
No description provided.
Delete branch "feature/aes-field-transformations"
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?
Use a fixed field-inverse addition chain and fixed coefficient/tweak reductions for AES and XTS, preserving the existing outputs.
The profiling byte count is actual transformed data; the logical address is tweak metadata. Host timings do not establish native performance or timing independence. This replaces the arithmetic portion of #5.
WIP: Use fixed AES field transformationsto Use fixed AES field transformationsReady for review. Fixed transformations preserve the independent arithmetic controls, and the original schedule-retirement prerequisite is integrated into this branch. The selected profiling example keeps transformed bytes separate from logical-address metadata.
Independent ciphertext checks exposed a pre-existing CBC-CS3 format defect that round-trip tests missed. It is tracked in #10 and corrected by #11, including aligned inputs. The field-transformation and key-owner changes here retain their original scope; use the corrective dependency before adopting standard CTS ciphertext.