3 ms·
A mechanistic certificate issuance service which is explicitly capable of being re-homed under another TA: Just use ACME compliant certbot calls to letsencrypt
by ggm 5y ago
A mechanistic certificate issuance service which is explicitly capable of being re-homed under another TA: Just use ACME compliant certbot calls to letsencrypt and you will have a certificate about "you" which validates under another TA.
I get your beef with google service availability longterm and the google list of killed products, but this is an instance of a service which in true Internet form "routes around damage"
This isn't the killer "what if google stop" problem area. ACME based certification doesn't care: find another TA, and move on with your life.
- kadoban 5y agoFor now. In a couple of years when Google gets bored and breaks the spec in incompatible ways, then the lock-in begins.
- binkHN 5y agoYes; the embrace, extend, extinguish playbook.
- ggm 5y agoIf they change the spec and certbot follows them, I doubt it will deprecate the non-google approaches. If they do something novel like enable multi-level wildcarding not just the terminal leftmost *. form, People might get stuck on how that works, but it would probably require chrome to change too. mainly I suspect this is to pacify people inside GKE who don't like calling outside of the protected space to get certificates to exist.
- bruce511 5y agoI guess my point is, LE exists, I'm using it already, why would I switch? Assuming there is a reason to switch, the switch back is not without cost. Ergo, either way, I'm not using this. Then again I don't use GCP for the same reason. My bigger point is that logical or not, my perception appears to be common. And that may hurt Google's ability to get traction with unique services in the future. No one cares about Google's CA, but perhaps this perception issue is a real problem?
- ggm 5y agoThats a good, valid set of points