Arsène von Wyss

@jayjupdhig Your suggestion has been received, thank you. This would require some adjustments in the https://github.com/ridercz/AutoACME/blob/master/Deploy/package.cmd file.

I'm reopening this since it has not been implemented yet.

Under the hood AutoACME uses [Certes](https://github.com/fszlin/certes) for LE interaction. I haven't checked the code, but using ES256, ES384 or ES512 as key algorithm may actually do the trick, see https://github.com/fszlin/certes/blob/main/src/Certes/KeyAlgorithm.cs

Thank you very much for your feedback! I'll add this to the documentation.

Revoking as CLI operation would be good, but... Does this indeed prevent the expiry email from being sent? I had previously re-issued new certs for domains and still got expiry...

I'd like to see wildcard support, and it may not be as complicated as it seems. The DNS challenge can be redirected to any other record by the means of...

The changes in #33 addresses some of the v2 topics. - ACMEv2 protocol is used - Basic "manual" support for SAN certificates is built in (see #4 for details) -...

@NenoLoje Releases are in @ridercz responsibility. In the meantime you could build it yourself, my version with DNS, SAN and wildcards has been running successfully for weeks now in my...

@bbakermmc Yes, wildcard has been merged into AutoACME. Wildcard however works only with DNS, please have a look at this wiki page: https://github.com/ridercz/AutoACME/wiki/AutoACME-in-a-web-farm-environment#operation-with-dns-challenge These changes were contributed by me and...

@JashanChittesh @RyanDansie The current release is actually using the ACMEv2 protocol (and it also supports DNS-based wildcard and SAN requests). However, it is not a .NET Core rewrite and it...