Skip to content

Conversation

@josevalim
Copy link
Member

@voltone @GriffinMB do you see any concerns with allowing a custom AAD when additional content needs to be added to the integrity?

RFC 7518 specifies empty and we already defaulted to A128GCM, which is preserved, but I wonder if you have any concerns.

Thank you!

@houllette
Copy link

I think it makes sense to allow this flexibility! Worth noting for posterity that while customizing the AAD doesn't provide any greater sense of cryptographic strength, it does provide another avenue of authenticating the decryption request and this change exposes that ability to the user.

@josevalim
Copy link
Member Author

Thank you @houllette, precisely that. We want to encrypt metadata into Livebooks, and we were planning to pass the notebook itself as AAD.

@houllette
Copy link

Awesome! You shouldn't have a problem with doing that provided the entire Livebook your passing in is smaller than 2.31 exabytes 🙂 (since AAD has a 264 bit maximum)

@GriffinMB
Copy link
Contributor

+1, no concerns with supporting custom AAD!

@josevalim josevalim merged commit 62022da into main Mar 10, 2023
@josevalim
Copy link
Member Author

💚 💙 💜 💛 ❤️

@josevalim josevalim deleted the jv-custom-aad branch March 10, 2023 07:53
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.

4 participants