jmccl
jmccl
As an aside 'eprintln!' goes to the error log which is pretty useful, although not what you're proposing.
I'm not aware of any reason the library should not work with Acme providers other than Let's Encrypt, although I haven't tried any others. Which one(s) are you thinking of...
Have you tried this out with Google Trust Service? My quick look at the docs suggest you need to deal with some Google specific account stuff.
Thanks for the suggestions. I'm (again) busy (well, on vacation this time) and will respond mid-next week.
I’m pretty sure I don’t want to implement the second bullet (have the callback return true or false) as the library currently handles errors by throwing and I don’t want...
Adding a _void *_ parameter is a non-starter for me. It's C-style type-unsafe code. In addition it would break existing clients and I'm unwilling to add the complexity required to...
I decided to check the patch in the prevoius comment in. It's a better interface and I shouldn't break any existing clients. I'm not sure the _std::function_ flexibility will be...
I think I construct the JSON manually because I started the code before I needed to parse the JSON responses. After I decided to use the library to parse the...
BTW, I'll leave this open until I get a Windows action in place and get the documentation updated.
Windows support is now in the README and there's a github action for it.