mirror of
https://github.com/FiloSottile/mkcert.git
synced 2026-04-25 05:26:03 +03:00
[GH-ISSUE #107] Chrome reporting ERR_SPDY_INADEQUATE_TRANSPORT_SECURITY #59
Labels
No labels
TLS stack issue
Windows
bug
duplicate
duplicate
enhancement
help wanted
help wanted
pull-request
question
question
root store
waiting for info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/mkcert#59
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @x2rider on GitHub (Jan 8, 2019).
Original GitHub issue: https://github.com/FiloSottile/mkcert/issues/107
A search on this error reports:
A deployment of HTTP/2 over TLS 1.2 SHOULD NOT use any of the cipher suites that are listed in the cipher suite black list.
I'm not sure how to change the cipher, or possibly the cipher order.
Is there something I can to do, to fix this?
@adamdecaf commented on GitHub (Jan 8, 2019):
What version of chrome are you using?
@FiloSottile commented on GitHub (Jan 8, 2019):
This sounds almost certainly like an issue with the HTTPS server implementation you are using, not with the certificate mkcert generated. mkcert has no control over the cipher suites your TLS implementation uses.
If it works with any other certificate, please reopen the issue.
@x2rider commented on GitHub (Jan 11, 2019):
I was able to fix the issue I was having by running the IIS Crypto 2 tool
https://appuals.com/fix-err_spdy_inadequate_transport_security/