ACME V2 client for C#

Client dev
1

Just to let people know, I implemented a client for ACME v2 for .NET projects.

This is a single file with a dependency only on JSON.Net.

Code:

Details:
https://ayende.com/blog/181281-A/building-a-lets-encrypt-acme-v2-client?key=22a2d96a17a44b478c0736719906367f

3 Likes
2

Hi Ayende,
Always great to see a simple example for the API, I’m starting to look at what changes we need to make for
Certify SSL Manager: https://certifytheweb and the temptation to write our own bits instead of using a library can be quite strong! DNS challenges are an interesting one, because there are so many DNS API’s people could potentially be using.

1 Like
3

Just to clarify, this does not handle any actual DNS update, so the client is entirely agnostic to this. I explicitly marked that as not related to the responsibilities of the client, precisely for the reasons you mentioned.

4

I know you prefer to implement your own client but have you also seen the certes implementation? https://github.com/fszlin/certes/ - I think that’s one to watch based on the relatively straightforward and thorough implementation.

5

Thanks for sharing!

I will definitely look into it how you used some system functions better. I’m not a C# dev and haven’t that much of experience with it.
In my PowerShell implementation I had to use a lot of the old COM api, wrote parts of an ASN.1 encoder and even had to call a C function (from the old crypt32.dll). Would be great to replace some of it.

6

@webprofusion When I started writing it, Certes didn’t support it :slight_smile:
However, we used to use Certes, but we moved to our own because we needed really fine grained control over the certificate generation. It also simplify dependency management somewhat.

1 Like
7

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.