Public key pinning support

I see that cert pinning is supported, but how much extra work would it be to add a method for pinning just a public key?

This would be much more convenient in most cases I think, given that key pairs are generally long-lived while certificates change on a regular basis — more so now with the rising popularity of Let's Encrypt which issues 90-day certs. With public key pining, I can just commit the public key (or hash) as a static file once and forget about it, whereas it seems like cert pinning would require me to implement additional logic to ensure that the latest version of the cert is always stored locally.

(Note: I've looked at the readme, but haven't yet used this library or done much digging into how Android, iOS, or the linked libraries handle TLS pinning; so my assumptions about what is and/or can be supported may be completely off.)

Commencez par la description existante du certificate-pinning dans le README, puis examinez les intégrations de TLS-pinning pour Android et iOS mentionnées dans l’issue. Déterminez si les bibliothèques liées prennent en charge le pinning de clés publiques ou de hashes, et définissez l’API ainsi que le comportement de vérification nécessaires ; le travail est terminé lorsque le périmètre est décidé et implémentable.