lukas2511

i recommend adding a shell-alias for this

Well, i'll have to check if the syntax i used works under BSD sed, because that seems to differ slightly and I ran into problems in the past.

Well, there are two major reasons why I think letsencrypt is great right now.

One thing is that it just works, it's a trusted CA and there is no bullshit "please install this cert" stuff.

The other thing is the automatisation. There were some CAs with free certificates before, but you had to manually click around in a webinterface, manually put a file on a webserver or copy an ID from an email, or whatever to verify that you are the owner of the domain. This process often took from around 30 minutes to several hours, while the acme-protocol is designed to handle validation in seconds, and it actually works. You can start a new project, send of the signing command, and in seconds you'll have a certificate.

Hey there, author of this thingy here, nice to see that some people like what i'm wasting my time on ;)

Just wanted to let you know that I just pushed a few updates, the code now no longer requires perl, uses the more generic shasum tool, uses base64 in openssl instead of the systems base64 binary, and some more stuff.

There are a few more dependencies I want to get rid of, like 'sed'. But 'openssl' and 'curl' will stay as depdencies.

I also want to expand this script with the ability to detect changes in the domain config and with a check if a certificate is about to expire so that it can be renewed in a cron-job or something similar.

Revocation is another thing that I kinda should look at, for now you'll have to do that with one of the other clients that has this option.

And thanks to the author of acme-tiny, which kinda inspired me to write this.