Generador de SSL Pinning
Genera configuraciones de SSL pinning para Android e iOS
Guía de Estrategia de Pinning
Certificado Hoja (Leaf)
High security, but changes frequently (e.g. every 90 days). Requires app updates before every expiration.
CA Intermedia
Recommended. Changes rarely (years). Good balance between security and maintenance.
CA Raíz
Máxima estabilidad (10-20 años). Confía en todos los certificados emitidos por esta Raíz. Mantenimiento mínimo.
Guía de Pin de Respaldo
Para prevenir la rotura de la app si tus claves son comprometidas o perdidas, DEBES incluir un pin de respaldo. Genera un Par de Claves de repuesto offline y guárdalo seguro.
1. Generar Par de Claves de Respaldo:
openssl genrsa -out backup_key.pem 2048
2. Extraer Pin SPKI:
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.