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

Align guidance on Public-Key-Pinning #107

Open
rbsec opened this issue Sep 6, 2019 · 2 comments
Open

Align guidance on Public-Key-Pinning #107

rbsec opened this issue Sep 6, 2019 · 2 comments

Comments

@rbsec
Copy link
Contributor

rbsec commented Sep 6, 2019

The web security guidance recommends the use of public key pinning on high value sites, with warnings about the risks of implementing it.

However the MDN Documentation for public key pinning states that it's deprecated and should not be used:

This feature is no longer recommended. Though some browsers might still support it, it may have already been removed from the relevant web standards, may be in the process of being dropped, or may only be kept for compatibility purposes. Avoid using it, and update existing code if possible; see the compatibility table at the bottom of this page to guide your decision. Be aware that this feature may cease to work at any time.

The headers are no longer supported from Chrome, and the MDN documentation recommends fairly strongly against it, so should it be removed from this guidance? If not, maybe MDN should be updated to match this so there's a consistent position on its use?

@atombrella
Copy link
Contributor

@april

@april
Copy link
Contributor

april commented May 5, 2020

Good call, I'll probably remove it entirely. I do need to update the Observatory at the same time.

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

3 participants