SSL Pinning Generátor
Hozzon létre SSL pinning konfigurációkat Android és iOS rendszerekhez
Pinning Stratégiai Útmutató
Leaf Tanúsítvány
High security, but changes frequently (e.g. every 90 days). Requires app updates before every expiration.
Köztes CA
Recommended. Changes rarely (years). Good balance between security and maintenance.
Root CA
Maximális stabilitás (10-20 év). Minden ezen Root által kiadott tanúsítvány megbízható. A legalacsonyabb karbantartási igény.
Tartalék Pin Útmutató
Az alkalmazás működésének megakadályozása érdekében, ha a kulcsok sérülnek vagy elvesznek, KÖTELEZŐ tartalék pint is megadni. Generáljon egy tartalék kulcspárt offline, és tartsa biztonságban.
1. Tartalék Kulcspár Generálása:
openssl genrsa -out backup_key.pem 2048
2. SPKI Pin Kinyerése:
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.