SSL Pinning генератор
Генерирайте SSL pinning конфигурации за Android и iOS
Ръководство за Pinning стратегия
Leaf сертификат
High security, but changes frequently (e.g. every 90 days). Requires app updates before every expiration.
Междинен CA
Recommended. Changes rarely (years). Good balance between security and maintenance.
Root CA
Максимална стабилност (10-20 години). Доверява се на всички сертификати, издадени от този Root. Най-ниска поддръжка.
Ръководство за резервен Pin
За да предотвратите счупване на приложението, ако ключовете ви бъдат компрометирани или загубени, ТРЯБВА да включите резервен pin. Генерирайте резервна двойка ключове офлайн и я пазете на сигурно място.
1. Генерирайте резервна двойка ключове:
openssl genrsa -out backup_key.pem 2048
2. Извлечете 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.