Skip to content
This repository was archived by the owner on Jun 14, 2024. It is now read-only.

HPKP - Public Key Pinning id points to the wrong entry in chrome status #449

Open
martinsuchan opened this issue Sep 1, 2016 · 4 comments
Labels

Comments

@martinsuchan
Copy link

This page shows that HTTP Public Key Pinning (HPKP) is not supported in Firefox.

It works in Firefox since v35.
http://caniuse.com/#feat=publickeypinning
https://developer.mozilla.org/en/docs/Web/Security/Public_Key_Pinning

@ghost
Copy link

ghost commented Sep 2, 2016

The status is fetched from https://www.chromestatus.com/features/4669935557017600. It needs to be updated by Chromium team on their side. You need to file a bug on chromium-dashboard.

@stof
Copy link

stof commented Sep 14, 2016

@nextprime the chromium-dashboard status you linked is about the HPKP reporting feature, not about HPKP itself.

@ghost
Copy link

ghost commented Sep 15, 2016

@stof You're right. I didn't notice that. So https://github.com/MicrosoftEdge/Status/blob/production/status.json#L4182 should be changed. Another thing is since Firefox supports HPKP blocking but not reporting, should the status page reports HPKP is supported or not supported in Firefox? Unfortunately Edge status page doesn't indicate partial support.

@molant molant changed the title Firefox already shipped HPKP - Public Key Pinning HPKP - Public Key Pinning id points to the wrong entry in chrome status Jan 4, 2018
@molant
Copy link
Contributor

molant commented Jan 4, 2018

There is no entry to track support for HPKP in Chrome status. We should remove the id and put the data manually.

@molant molant added the bug label Jan 4, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants