Public-Key-Pins-Disabled/EN/Background: Unterschied zwischen den Versionen
| Zeile 1: | Zeile 1: | ||
| − | One of the most difficult headers for non-experts to configure. If you have a [[Certificate|SSL certificate]], you can communicate to the requesting browser how long the certificate will still be valid, and send a "key" as a unique identification. On the next request, the browser can then check whether the certificate is still the original certificate. If an attacker tries to offer a forged certificate to the user, the web browser will not send any data and not display any information. Further information about Public Key Pinning: [https://developer.mozilla.org/en-US/docs/Web/HTTP/Public_Key_Pinning Public Key Pinning (HPKP)]. | + | One of the most difficult [[Header/EN|headers]] for non-experts to configure. If you have a [[Certificate|SSL certificate]], you can communicate to the requesting browser how long the certificate will still be valid, and send a "key" as a unique identification. On the next request, the browser can then check whether the certificate is still the original certificate. If an attacker tries to offer a forged certificate to the user, the web browser will not send any data and not display any information. Further information about Public Key Pinning: [https://developer.mozilla.org/en-US/docs/Web/HTTP/Public_Key_Pinning Public Key Pinning (HPKP)]. |
Aktuelle Version vom 8. April 2019, 09:54 Uhr
One of the most difficult headers for non-experts to configure. If you have a SSL certificate, you can communicate to the requesting browser how long the certificate will still be valid, and send a "key" as a unique identification. On the next request, the browser can then check whether the certificate is still the original certificate. If an attacker tries to offer a forged certificate to the user, the web browser will not send any data and not display any information. Further information about Public Key Pinning: Public Key Pinning (HPKP).
