Skip to content

Make Security Considerations an explicitly named section? #267

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

Closed
chaals opened this issue Jan 4, 2023 · 2 comments
Closed

Make Security Considerations an explicitly named section? #267

chaals opened this issue Jan 4, 2023 · 2 comments

Comments

@chaals
Copy link
Contributor

chaals commented Jan 4, 2023

It's helpful, even in a short spec where the bulk of security considerations are described in a single place to have an explicit revision of them that can be found. Unlike with a very large spec, the task of doing that for yourself probably isn't beyond the average implementor, so this is merely an editorial suggestion.

@marcoscaceres
Copy link
Member

marcoscaceres commented Jan 5, 2023

We originally listed them but then baked them back into the algorithms at the request of the Sec folks. #245

If it’s ok, we’d like to keep it as is.

@chaals
Copy link
Contributor Author

chaals commented Jan 5, 2023

I'd prefer it were possible to find them in one go as well - I do like that they are mentioned directly in relevant places, I just want everything :). But I can live with it as is - as mentioned, the spec isn't massive so it's feasible to find them all on my own....

@chaals chaals closed this as completed Jan 5, 2023
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

2 participants