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

Clarify HTTP validation requirements #374

Open
wthayer opened this issue Jul 14, 2022 · 2 comments
Open

Clarify HTTP validation requirements #374

wthayer opened this issue Jul 14, 2022 · 2 comments

Comments

@wthayer
Copy link
Contributor

wthayer commented Jul 14, 2022

The two HTTP validation methods (.6 and .19) do not specify requirements for honoring HSTS and, when validation is performed over HTTPS, validating the certificate. I propose that we explicitly define these requirements. I think it is common practice for CAs not to honor HSTS or validate certs when performing domain name validation.

@timfromdigicert
Copy link
Contributor

Are you suggesting that if I put a self-signed certificate on my domain example.com, that validation should fail because the certificate is not valid? What is the point of that, since HTTP validation is allowed and would succeed?

I support explicitly defining the requirements (for clarity), but couldn't they be as simple as "you can ignore HSTS and certificate validity for HTTPS" ?

@wthayer
Copy link
Contributor Author

wthayer commented Jul 14, 2022

I support explicitly defining the requirements (for clarity), but couldn't they be as simple as "you can ignore HSTS and certificate validity for HTTPS" ?

Yes, I think so, but I've been around this group long enough that I'm not going to assume it's that simple.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants