aloyr / acme-tiny-automator Goto Github PK

Subject alternative name is important in some use-cases and need to be accounted for in the main program.

As luck would have it, acme-tiny already processes a CSR properly if it has a SAN section, so we need to add the handling of it in the main program.

What I'm thinking is to keep the first parameter as primary domain and use the remaining parameters as SANs.

The examples configuration file can also serve as a defaults file in some cases. FHS and General file organization for Apache and nginx varies considerably between Linux distro families.

It would be nice to have default values that cover other distros as well. Even if these values were commented out, they would still help guide users of other Linux favors.

As a prototype, this script assumes it lives in the same location as the configuration. It would be more appropriate to assume the script(s) will end up at a folder like "/usr/local/bin" and the configuration file on "/etc/sysconfig" or "/etc/defaults"

Create a 1-line setup script to help folks get started.

The mechanics should work like one-liner setups used elsewhere, like in the system-Config-files repo, as outlined in its README.md

The letsencrypt certificate has a fairly short lifespan – currently three months. It would be nice to have a system in place to automate renewals of these certificates.

Since all certificates created are in one location defined in the Config file, the renewal check routine could just go over the CRT files in there and process renewals automatically.

To keep things simple, the existing script could be extended to cover renewals. The trigger for renewals could be the first and only parameter being "renew".

Ideally, this check would be put on a daily cron.