Background

After a long hiatus between releases we are happy to finally announce a new version of win-acme, containing more than two years worth of new features, enhancements, plugins and bugfixes.

The new version is a home-coming of sorts, using code from simple-acme, a fully compatible fork of win-acme that has been maintained by the same developers over the past couple of years. Moving forwards, development and support for both versions will happen in the simple-acme repository. Releases will happen more or less simultaneously for both editions of the client.

Because win-acme is being sponsored by ZeroSSL, from this version onwards they will be the default provider for all new win-acme installations. Not to worry though, because existing installations are not affected and this project remains committed to supporting all other free and commercial ACME services just as well.

Upgrading

The new version is drop-in compatible with all previous releases of win-acme v2.1 or higher, save for a couple of details listed below. Users of win-acme v2.0 should read the upgrade steps to v2.2 first before installing a v2.4 or higher release.

Breaking changes

• Reference scripts are no longer distributed with the program. The fact that these scripts were "in the box" suggested that they had the same level of support, quality assurance and guaranteed backwards compatibility that users enjoy for the main program, while that was simply not the case. We have encouraged users to review and test the scripts before using them for a while now, but forcing a separate download from the reference scripts shifts the responsibility even more clearly. As a secondary goal, we also hope to reduce the amount of false positives from anti-virus solutions, which may be triggered by these scripts touching all kinds of vital infrastructure.
• The IIS target plugin will use - instead of , as a separator when generating friendly names for certificates to make them more easy to use in CSV format required for some bulk commands. This should affect very few users, but if you use scripts or software that relies on a hardcoded friendly name - and you have not specifically configured that same friendly name for the renewal - now would be good time to do so, by setting the FriendlyName property in the .renewal.json file or by reconfiguring the renewal from scratch. Alternatively, change your installation script to use the {FriendlyName} argument.
• For plugin developers: upgraded .NET runtime from version 7.0 to 10.0 and minor changes to interfaces.
• For new installations: the default ACME endpoint is changed to https://acme.zerossl.com/v2/DV90. You can change this via the command line using the --baseuri parameter and/or by updating the default in settings.json. For example you can use https://acme-v02.api.letsencrypt.org/ to change it to Let's Encrypt, which was the previous default.

Full changelog

Check it our here.