Gerador de SSL Pinning
Gerar configurações de SSL pinning para Android e iOS
Guia de Estratégia de Pinning
Certificado Folha (Leaf)
High security, but changes frequently (e.g. every 90 days). Requires app updates before every expiration.
CA Intermédia
Recommended. Changes rarely (years). Good balance between security and maintenance.
CA Raiz
Estabilidade máxima (10-20 anos). Confia em todos os certificados emitidos por esta Raiz. Menor manutenção.
Guia de Pin de Backup
Para evitar a quebra da app se as suas chaves forem comprometidas ou perdidas, DEVE incluir um pin de backup. Gere um Par de Chaves de reserva offline e guarde-o em segurança.
1. Gerar Par de Chaves de Backup:
openssl genrsa -out backup_key.pem 2048
2. Extrair 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.