Skip to content

Conversation

@BernhardBln
Copy link

@BernhardBln BernhardBln commented Jan 20, 2026

@uweschaefer this is a draft that should be backward-compatible, and automatically enable random iv for new containers, also when a fix iv is set.

I haven't thought it through completely if this 100% safe, will do in the next days.

Closes #1462

@BernhardBln BernhardBln changed the title draft Draft - Randomly generated IV, backward-compatible Jan 21, 2026
- Not mandatory anymore to set a iv for the JDKCryptoEngine
- No matter if a fixed iv is set or not, new containers will use random ivs
- The iv is stored as a separate field in a crypto container
- Containers created with a fix iv still get decrypted if the iv is configured

removed comment
@BernhardBln BernhardBln force-pushed the optional-iv branch 2 times, most recently from 7b7c515 to 8cf79d6 Compare January 21, 2026 06:26
As different engines probably have different needs.
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.

cryptoshred.initVector

1 participant