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

Strict Transport Security not implemented well #8

Open
plange opened this issue Feb 8, 2011 · 0 comments
Open

Strict Transport Security not implemented well #8

plange opened this issue Feb 8, 2011 · 0 comments

Comments

@plange
Copy link
Contributor

plange commented Feb 8, 2011

There are some conflicts between the STS standard and the DANE specification.

The current STS draft states[1]:
from section 2.2:
2. The UA terminates, without user recourse, any secure transport
connection attempts upon any and all secure transport errors or
warnings, including those caused by a site presenting self-signed
certificates.

This means we cannot use dane certificate associations for self-signed certificates together with STS. We currently work around this problem by rewriting the URL to HTTPS, but we feel that this is an ugly solution.

Todo:

  • Work on consensus between standardisation boards

[1] http://tools.ietf.org/html/draft-ietf-websec-strict-transport-sec-00

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