Closed kendallb closed 4 years ago
Oh man... same here. I was just getting started with ACMESharp, and I guess I need to abandon it now. :-(
I want to use the staging server, and even without that, I can't rely on a solution that stops working in a month.
You should either move to using ACMESharp Core which fully supports V2:
https://github.com/PKISharp/ACMESharpCore
Another option that I ended up using is Certes, mostly as it has a simpler API and my needs were very simple:
Thanks, kendallb. However, I can't find any docs on it. For example, I can't install the module the same way as I can with ACMESharp:
Install-Module -Name ACMESharpCore
Is there a "Quick Start" (or other) documentation for ACMESharpCore?
Oh you are looking for the PowerShell integration? I am not familiar with ACMESharp Core, so you might want to ask over there. I don't know if they have powershell support, but it looks like there is a separate project for that:
https://github.com/PKISharp/ACMESharpCore-PowerShell
Certes has command line support, so maybe that would do what you need also?
I don't care about PowerShell integration... I just want instructions on how to actually do something with it.
If you're just looking for a tool that can let you generate certs from the command line, you can either use the ACMESharpCore-PowerShell tool mentioned above, or there is an example CLI project in the ACMESharpCore project that let's you do most things that folks need.
As far as updating this project to v2, I'm afraid I don't have any time or plans to do that myself. If others wish to dive in and make the changes, all contributions are welcome, but the ACMESharpCore project was my attempt to move to the latest.
Well this is extremely annoying. They just deprecated the ACME v1 API for staging, and it is going away in production in November. Unfortunately while the new ACMESharpCore library supports the v2 protocol, the API is completely different so my code needs to be completely re-written.
How much work would be involved in updating this library and it's existing API's to support the v2 protocol, so those who invested time writing code to the older API's can avoid a complete re-write before November?