3 ms·
This is exactly the sort of cruft that's quite rarely used and should be omitted from a lean implementation. I'm not aware of any serious use of RFC 6091. Gnu
by mcpherrinm 10y ago
This is exactly the sort of cruft that's quite rarely used and should be omitted from a lean implementation.
I'm not aware of any serious use of RFC 6091. GnuTLS supports it, but I don't think any other implementations do.
- teddyh 10y ago> I'm not aware of any serious use of RFC 6091. Was it really your intention to dismiss my application¹ as not serious? ① https://www.recompile.se/mandos https://www.recompile.se/mandos
- mcpherrinm 10y agoIt may be serious but I wasn't aware of it. It seems your project could use x509 client certs as well as gpg ones if you wanted to use a different TLS library that didn't support GPG.
- teddyh 10y agoThat seems like a bit of circular reasoning. We use RFC 6091 because it’s the best fit for our problem, and allows us to avoid the needless complexity of X.509 certificates, which has caused many bugs in the past (in essentially all TLS libraries).
- mcpherrinm 10y agoUsing an obscure feature of one TLS library seems like a bad strategy for avoiding bugs. If compatibility doesn't matter, I'd probably use something less crufty, like http://noiseprotocol.org/ http://noiseprotocol.org/