Re: Assorted questions and musings, Re: So has anybody come up with a solution for certificate automation that will work on a Midrange box?

It seems to me that if the supplied web server is a "real" Apache httpd, then the locations of the keys and certs *should* be in the
configuration files, reachable through WRKLNK and EDTF.

On 4/3/26 11:54 AM, Pete Helgren wrote:

It doesn't factor in until then, but that is your issue, you want to secure your connection with TLS.

Actually, no, we're already doing that, on multiple customer boxes, and have been for quite a few years now. The object is to do so in a way that is amenable to fully automated maintenance, of the sort that LE has been doing from its inception, and that other CAs are evidently also rolling out.

I don't know about any of you, but the idea of having, three years from now, to manually deal with certs that last a maximum of a month and a half (and do so in a server that has to be restarted for the changes to take effect) makes me want to (with apologies to George Washington) "retire to the back-country, and live in a wigwam."

--
JHHL

--
JHHL