3 ms·
As I understand it, they are also removing raw public keys and OpenPGP keys, keeping only X.509 certificates.
by teddyh 10y ago
As I understand it, they are also removing raw public keys and OpenPGP keys, keeping only X.509 certificates.
- hdhzy 10y agoDid anyone use OpenPGP for this? Seems interesting...
- teddyh 10y agoThe project I co-designed still use this. It’s also supported by mod_gnutls for Apache.
- hdhzy 10y agoIs this only to check server identity or client as well? Why not use regular X 509 certs?
- teddyh 10y agoOnly server identity. Our situation in our project is that the TLS server side already has an OpenPGP key for other purposes anyway, so it is very practical to use it as an identity check inherent in the TLS handshake. On the topic of X.509 certificates, I can only point to Peter Gutmann: Everything you Never Wanted to Know about PKI but were Forced to Find Out (https://www.cs.auckland.ac.nz/~pgut001/pubs/pkitutorial.pdf https://www.cs.auckland.ac.nz/~pgut001/pubs/pkitutorial.pdf) Basically, X.509 certificates are very complex, and many security bugs have historically been found in the parsing code for them.
- snakeanus 10y agoWhich is quite sad since OpenPGP keys, unlike X.509 certificates, are allowed to carry signatures from multiple private keys instead of just one.
- hdhzy 10y agoFrom the github repo looks like raw public keys are supported but openpgp not : https://github.com/tlswg/tls13-spec/issues/929 https://github.com/tlswg/tls13-spec/issues/929 https://github.com/tlswg/tls13-spec/issues/937 https://github.com/tlswg/tls13-spec/issues/937