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.)

Comienza con la descripción existente de certificate-pinning en el README y, después, inspecciona las integraciones de TLS-pinning para Android e iOS mencionadas en el issue. Determina si las bibliotecas enlazadas admiten el pinning de claves públicas o de hashes y define la API y el comportamiento de verificación necesarios; se considera terminado cuando el alcance esté decidido y sea implementable.