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

sa_ktls and sa_cipher (KTLS_CIPHER_AES_GCM_128) #16

Open
nmav opened this issue Apr 8, 2016 · 0 comments
Open

sa_ktls and sa_cipher (KTLS_CIPHER_AES_GCM_128) #16

nmav opened this issue Apr 8, 2016 · 0 comments

Comments

@nmav
Copy link
Member

nmav commented Apr 8, 2016

I like the approach with fixed values (that's a type-safe userspace API), however it may cause upstream opposition. Be prepared to be asked to use directly the "rfc5288(gcm(aes))" string from userspace. There are good arguments to not use it (such as ability to change the internal API, and type safety).

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

1 participant