> I understand the reason letsencrypt came into existence is the web. So > most environments where acme-client currently is used probably already > have a httpd running. But I suspect the demand for acme-client on > non-webservers will rise and it will feel more like a kludge to > configure, start and stop a webserver in those environments.
I really hope not. Don't forget that letsencrypt is still a part of the CA cabal.
