Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Secure content not tested IV size other than 96 bits #89

Open
jordig100 opened this issue Oct 19, 2023 · 1 comment
Open

Secure content not tested IV size other than 96 bits #89

jordig100 opened this issue Oct 19, 2023 · 1 comment
Assignees

Comments

@jordig100
Copy link
Collaborator

The spec says:

For the purposes of this specification, AES-GCM SHOULD be used with a 96-bit Initialization Vector (IV), 128-bit Authentication Tag (T) and it MAY contain an optional Additional Authenticated Data (AAD). The cipher text is stored in the file path defined in the parent element with the cypher file format defined in Appendix D. 3MF Cipher File Format.

This means that other IV sizes are also valid. The 96-bit is the recommended size.

@JimZuber
Copy link
Collaborator

The test specification does state "All test cases will use a 96 bit initialization vectors and 128 bit tags, although other lengths are allowed by the secure content specification.", so this isn't a surprise. However, it would certianly be easy to add test cases that use other initialization vector bit lengths if desired

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

No branches or pull requests

2 participants