Re:Automate Public Certificates Lifecycle Management via RFC...
by bruce511 on Tuesday April 12, 2022 @12:53AM
(#30998759)
I 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?
Re:Automate Public Certificates Lifecycle Management via RFC...
by ggm on Tuesday April 12, 2022 @01:24AM
(#30998922)
Thats a good, valid set of points
Re:Automate Public Certificates Lifecycle Management via RFC...
by kadoban on Tuesday April 12, 2022 @12:06AM
(#30998491)
For now. In a couple of years when Google gets bored and breaks the spec in incompatible ways, then the lock-in begins.
Re:Automate Public Certificates Lifecycle Management via RFC...
by binkHN on Tuesday April 12, 2022 @12:30AM
(#30998641)
Yes; the embrace, extend, extinguish playbook.
Re:Automate Public Certificates Lifecycle Management via RFC...
by ggm on Tuesday April 12, 2022 @01:30AM
(#30998959)
If 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.
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.