For historical reasons, we use the phrase Namecoin TLS Certificate as a magic string in quite a few places. Given that we are transitioning to a general-purpose PKI (not just TLS server auth), we should replace this string with something more accurate. I think Namecoin X.509 Certificate should be fine. Places that a GitHub organization search picks up that we need to update:
A few of these are obsolete for other reasons anyway, and this isn't a bad excuse to finally retire them. This change will break backwards compatibility, but since we're breaking backwards compatibility in the upcoming release anyway (due to the transition to stapled certifications), this is a particularly good opportunity to get this done.
For historical reasons, we use the phrase
Namecoin TLS Certificateas a magic string in quite a few places. Given that we are transitioning to a general-purpose PKI (not just TLS server auth), we should replace this string with something more accurate. I thinkNamecoin X.509 Certificateshould be fine. Places that a GitHub organization search picks up that we need to update:encaya/server/server.go
Line 912 in 7ef62a0
A few of these are obsolete for other reasons anyway, and this isn't a bad excuse to finally retire them. This change will break backwards compatibility, but since we're breaking backwards compatibility in the upcoming release anyway (due to the transition to stapled certifications), this is a particularly good opportunity to get this done.