I was confused for a second as well, but I think "systemd.software" is actually the domain of the website.
If the systemctl is what you're objecting to, on the other hand, then you need to get a grip.
If the systemctl is what you're objecting to, on the other hand, then you need to get a grip.
google certbot systemd or certbot openrc to see it fail. tack on that they had to invalidate all of their certs one day and gave little warning and you could easily have experienced revoked SSL certs if your system wasn't the default setup.
I'm sorry, what? Are you projecting? By what measure is "custom" and by what measure is "no one"? My old setup was very custom and worked quite fine with certbot. My current setup is less custom and still works quite fine with certbot. I literally haven't had any trouble whatsoever with certbot.
> the fact that they don't have easy guides on how to do it without certbot is worrying
Without Certbot we'd be using openssl's arcane command line. And you're absolutely right, openssl is a !@#$ing dumpster fire. I'd argue that openssl's garbage tools are exactly why certbot was created.
> google certbot systemd or certbot openrc to see it fail.
I did google certbot systemd and certbot openrc. I don't see failures. Please cite some.
> they had to invalidate all of their certs one day and gave little warning and you could easily have experienced revoked SSL certs if your system wasn't the default setup
"They" are LetsEncrypt. And "They" aren't Certbot.
In retrospect I thought I'd vouch for your message since I thought it would be a decently constructed argument. Instead I now recognize you didn't write a reasoned argument. That was my fault for vouching before reading.
If you don't like Certbot or LetsEncrypt then nobody's forcing you to use them. Go pay for a SSL certificate since you don't understand how to use free tools. Or just use unencrypted connections and let your users get hacked.