-
Notifications
You must be signed in to change notification settings - Fork 50
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
WPT tests are needed for serverCertificateHash feature #589
Comments
I've been told in the WPT channel that generating new certificates with a different algorithm wouldn't be a problem, so we can easily solve (2). Regarding the issue of having different certificates to check against by the tests, we may use the sub function of the WPT Pipes APIs to define a template for the server certificate, which will be resolved depending on the testing infrastructure where the tests run. |
Meeting:
|
What is the status of updated wpt tests for certificate hashes? |
I haven't had time to work on this lately. I don't have a clear idea of how to do it either, so if anybody has more time and knowledge, I'd be happy to reassign the issue. I totally agree that we need more tests for the serverCertificateHashes. |
I have tried to make some: |
There is only one test in the WPT repository to cover the functionality of this feature, which just checks an invalid hash doesn't match.
According to the WPT folks:
The main problems we have to implement tests in the WPT infrastructure are the following:
1- the feature imposes a restriction of 14 days maximum expiration time
2- the RSA keys are forbidden
Additionally, we would expect these WPT will be valid as well when they are executed by the browser's testing infrastructure, and as far as I know, the HTTP servers running there may have a different SSL certificate.
The text was updated successfully, but these errors were encountered: