▲ | grishka 4 days ago | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Isn't it usually the server's public key that's pinned? The key pair isn't regenerated when you renew the certificate. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
▲ | toast0 4 days ago | parent [-] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Typical guidance is to pin the CA or intermediate, because in case of a key compromise, you're going to need to generate a new key. You should really generate a new key for each certificate, in case the old key is compromised and you don't know about it. What would really be nice, but is unlikely to happen would be if you could get a constrained CA certificate issued for your domain and pin that, then issue your own short term certificates from there. But if those are wide spread, they'd need to be short dated too, so you'd need to either pin the real CA or the public key and we're back to where we were. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|