Skip to content

Request for clarification on the usage of Domain and Challenge Parameters #339

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

Open
Sh-Amir opened this issue Apr 15, 2025 · 3 comments
Open
Labels
future security-tracker Group bringing to attention of security, or tracked by the security Group but not needing response.

Comments

@Sh-Amir
Copy link

Sh-Amir commented Apr 15, 2025

This issue refers to the security review requested at w3c/security-request/#55.

In Section 2.1, I would recommend providing additional information or changing the wordings regarding the usage of "Domain" and "Challenge" parameters to better highlight the scenarios in which their usage becomes mandatory. I do agree that not all use cases demand replay protection, but it would be nice to make this explicit by providing examples or adding a note to better highlight this aspect.

@simoneonofri simoneonofri added the security-tracker Group bringing to attention of security, or tracked by the security Group but not needing response. label Apr 15, 2025
@TallTed

This comment has been minimized.

@Sh-Amir Sh-Amir changed the title Request for clarification on the uage of Domain and Challenge Parameters Request for clarification on the usage of Domain and Challenge Parameters Apr 16, 2025
@Sh-Amir
Copy link
Author

Sh-Amir commented Apr 16, 2025

in issue title, s/uage/use/

Thanks for pointing out the typo.

@brentzundel
Copy link
Member

We are grateful for this response from SING and look forward to considering it as part of a future version of the specification

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
future security-tracker Group bringing to attention of security, or tracked by the security Group but not needing response.
Projects
None yet
Development

No branches or pull requests

4 participants