SSL Pinning Ģenerators
Ģenerējiet SSL pinning konfigurācijas Android un iOS
Pinning stratēģijas ceļvedis
Leaf Sertifikāts
High security, but changes frequently (e.g. every 90 days). Requires app updates before every expiration.
Vidēja līmeņa CA
Recommended. Changes rarely (years). Good balance between security and maintenance.
Root CA
Maksimāla stabilitāte (10-20 gadi). Uzticieties visiem šī Root izdotajiem sertifikātiem. Zemākā uzturēšana.
Rezerves Pin Ceļvedis
Lai novērstu lietotnes darbības pārtraukumu, ja jūsu atslēgas ir apdraudētas vai pazaudētas, jums OBLIGĀTI jāiekļauj rezerves pin. Ģenerējiet rezerves atslēgu pāri bezsaistē un glabājiet to drošībā.
1. Ģenerēt Rezerves Atslēgu Pāri:
openssl genrsa -out backup_key.pem 2048
2. Izvilkt SPKI Pin:
openssl rsa -in backup_key.pem -pubout -outform der | openssl dgst -sha256 -binary | openssl enc -base64
SSL Pinning Generator creates certificate pinning configurations for mobile apps associating hosts with expected public keys, preventing MITM attacks even when a CA is compromised.
Key Facts
- Chrome removed HPKP in 2018 due to deployment risks
- Mobile apps widely use certificate pinning for API security
- Certificate Transparency logs reduce need for browser pinning
- Always include a backup pin for disaster recovery
Frequently Asked Questions
What is SSL pinning?
Hardcodes expected certificate/public key in client app, preventing forged certificate attacks even from trusted CAs.
Should I pin the certificate or public key?
Public key — survives certificate renewals. Certificate pinning breaks on every renewal. Always include backup pins.
What happens if I rotate my certificate?
If pinning the certificate, app breaks until updated. Use public key pinning with backup pins for safe rotation.