-
-
Notifications
You must be signed in to change notification settings - Fork 683
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
Cryptography - suggested modification of 6.5.4 #2497
Comments
OK for me after some wording changes. Some notes/comment on my own:
|
I leave this up to @danielcuthbert's judgement, I am not sure about this one. |
@randomstuff "Some of these schemes are currently not in the crypto appendix, should be add them?" <-- yes please if you have the time or i will do it this week. The appendix I feel is the best place for the list as it allows us to update that more frequently whereas we cant do this easily with core. |
@randomstuff is there any action on the requirement itself here or should we close this issue in favour of #2513? |
#2513 is about listing some missing MAC algorithms (in the appendix) while this one is about rewording the 6.5.4 which is weirdly formulated. Can we tweak 6.5.4 and 6.5.2 into something like:
And maybe have a dedicated section about approved authenticated encryption methods. Request feedback from @unprovable and @danielcuthbert |
I think these changes are fine and don't require further discussion.
What are you proposing for this? |
Sorry, I meant:
The idea is that is my wording we have:
So we need to actually have some approved authentication encryption methods (especially ChaCha-Poly1305 which is currently nowehere to be found in the appendix). Something like:
|
Ok so please open 2 PRs, one for V6 and one for the appendix. |
As discussed in #2590, maybe 6.5.2 should be merged into 6.2.2. |
Ok I merged #2597, what else for this issue @randomstuff? |
Anything else here @randomstuff ? |
I think we are finished with that. |
Current:
Proposed by Bart Preneel:
with comment:
The text was updated successfully, but these errors were encountered: