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

ccm gcm adjustments #18

Merged
merged 5 commits into from
Feb 27, 2020
Merged

ccm gcm adjustments #18

merged 5 commits into from
Feb 27, 2020

Conversation

hannesm
Copy link
Member

@hannesm hannesm commented Feb 26, 2020

see individual commit messages for more details

@hannesm
Copy link
Member Author

hannesm commented Feb 27, 2020

this changes the behaviour of GCM (now raise on empty IV), this is fine for the time being -- note that protocols on top of GCM (such as TLS - https://tools.ietf.org/html/rfc5288#section-3 where a 4 byte implicit salt (derived from KDF) and a 8 byte explicit nonce (transported in the packed) are used -- thus a bad packet (too short) will be detected before GCM.decrypt is called -- or phrased differently: any use of GCM in TLS will never provide an empty IV, but always one of 12 bytes) ensure that the IV will never be empty. there may be in the future a no-exception-leaking interface for mirage-crypto, but that may be rather inconvenient to use.

@hannesm hannesm merged commit 40dc0ff into mirage:master Feb 27, 2020
@hannesm hannesm deleted the ccm-gcm branch February 27, 2020 08:26
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.

None yet

3 participants