Package: simp-le-client
SimpleLet’s Encryptclient.simp_le--emailyou@example.com-faccount_key.json\-faccount_reg.json\-ffullchain.pem-fkey.pem\-dexample.com-dwww.example.com--default_root/var/www/html\-dexample.net:/var/www/other_htmlFor more info seesimp_le--help.NOTE: this repository is mostly unmaintained; I will review and merge PRs,
but I(@zenhack) am no longer using this tool myself and am thus not motivated
to otherwise actively develop it.Project History@kuba wrote the originalhttps://github.com/kuba/simp_le, at a time when
ACME & let’s Encrypt were very new; certbot still didn’t support nginx,
and there was an un-filled niche for a trivial command line ACME client.At some point @kuba stopped maintaining simp_le. A few months later bitrot
set in, and PRs fixing the problems went unmerged.When the breakage began to affecthttps://zenhack.net, I(@zenhack) forked
the project, merged the PRs, fixed CI and began maintaining the tool. This
continued for several years.I(@zenhack) switched over to using NixOS’s acme configuration options, and
transitioned the project to its current semi-unmaintained status.ManifestUNIX philosophy: Do one thing and do it well!simp_le--valid_min${seconds?}-fcert.pemimplies thatcert.pemis valid for at at leastvalid_min(defaults to 2592000
seconds / 30 days). Register new ACME CA account if necessary. Issue
new certificate if no previous key/certificate/chain found. Renew only
if necessary.(Sophisticated) “manager” for${webroot?}/.well-known/acme-challengeonly. No challenges other
thanhttp-01. Existing web-server must be running already.No magical webserver auto-configuration.Owner of${webroot?}/.well-known/acme-challengemust be able to
run the script, without privilege escalation (sudo,root,
etc.).crontabfriendly: fully automatable - no prompts, etc.No configuration files. CLI flags as the sole interface! Users
should write their own wrapper scripts or use shell aliases if
necessary.Support multiple domains with multiple roots. Always create single
SAN certificate persimp_lerun.Flexible storage capabilities. Built-insimp_le-ffullchain.pem-fkey.pem,simp_le-fchain.pem-fcert.pem-fkey.pem, etc.Do not allow specifying output file paths. Users should symlink if
necessary!No need to allow specifying an arbitrary command when renewal has
happened, just check the exit code:0if certificate data was created or updated;1if renewal not necessary;2in case of errors.--server(support multiple ACME v2 CAs).Support for revocation.Implicit agreement to the selected ACME CA’s terms of service.Installationsudo./bootstrap.sh./venv.shexportPATH=$PWD/venv/bin:$PATHUsage with DockerIf you want to use simp_le with Docker, have a look atsimp_le for Docker.HelpHave a look athttps://github.com/zenhack/simp_le/wiki/Examplesfor some examples.If you’re having problems feel free to open an issue to ask questions.Change LogBelow is a summary of changes introduced in each release. Any user-visible
changesmustbe recorded here. Note that the topmost entry sometimes
represents thenext(i.e. not yet released) version.Releases occur approximately every two months, unless there is a pressing need
to do otherwise (e.g. security & serious bug fixes), or no changes have been
made since the last release.0.20.0Update python-acme dependency to version 2.00.19.2Fix a minor standards conformance issue, seehttps://github.com/zenhack/simp_le/pull/1550.19.1Add missing dependency on thesixpackage.0.19.0Add--use_alt_chainflag.0.18.1Fix a minor protocol conformance issue.Fix some bitrot in the venv.sh script (not applicable unless installing
from the git repo).0.18.0Upgrade acme to 1.3 or later.Fix a bug where simp_le failed to obtain a cert from BuyPass ACME.0.17.0Upgrade acme to 1.x0.16.0Fix an ACME v2 protocol non-conformityUpgrade acme to 0.39.x0.15.0Please read these carefully, as this release includes a couple changes
that may require changes when upgradingSwitch from ACME v1 to ACME v2 endpoints support.
Support for ACME v1 endpoints has been dropped entirely.
If you were previously passing the server endpoint via the--serverflag, you will need to update it to point to
a v2 endpoint (or simply remove it, to use Let’s Encrypt’s
default v2 endpoint).Persist account_reg.json in addition to account_key.json, and
recover missing registration info if needed.You will now
need to pass a ``-f account_reg.json`` option to simp_leRemove the-fexternal.shfeature.Drop official support for Python 2 and 3.4.Add official support for Python 3.7 (in theory it should have
worked before, but we are now testing with it).Upgrade acme to 0.35.x0.14.0Upgrade acme to 0.33.x0.13.0Upgrade acme to 0.31.x0.12.0Upgrade acme to 0.29.x0.11.0Upgrade acme to 0.27.x0.10.0Upgrade acme to 0.25.x0.9.0Upgrade acme to 0.24.x0.8.1Add a workaround for some installation problems caused by a bug in pip.0.8.0Drop official support for Python 2.6Upgrade acme to 0.22.x0.7.0Remove the ToS hash comparison, implicitly agree to CA’s ToS if presentAdd check for empty or corrupt cert/key filesAdd some sanity checks for email syntaxUpgrade acme to 0.20.x0.6.2Implement the future-proofing mentioned in the 0.6.1 release notes. Future
TOS changes should not break simp_le >= 0.6.20.6.1Update the hash for the letsencrypt TOS. The TOS changed on November 15th,
which broke previous releases. Future releases will not hard-code the hash,
which should avoid this sort of problem in the future.0.6.0Drop official support for Python 3.3.Disable self-verification; this was highly unreliable and resulted in
spurrious warnings.Improve argument sanity-checks and error messages.Save account_key.json, even on failuresClean temporary challenge files.Upgrade acme to 0.19.x0.5.1Add a workaround for some installation problems caused by a bug in pip0.5.0Upgrade acme to 0.17.x0.4.0Upgrade acme to 0.16.x0.3.0Fix a bug where the version number was incorrectly reportedUpgrade acme to 0.15.x0.2.0Upgrade to acme 0.11.x0.1.1Change the package name; the original maintainer owns the simp_le PyPI
package, and hasn’t responded to requests to transfer it, so the package name
is now ‘simp_le-client’.0.1.0First release