Open Neville2312 opened 8 years ago
The build is failing, I think it needs to be upgraded to .NET Core 1.0 final (it's still using rc1). I don't have time for that right now, but I would accept a pull request :).
I got this to build in VS2015 by removing the .Net Core options. It is working fine for me in .Net 4.6, and I added a "directory" challenge provider, which basically means it puts the token in a directory specified in the command line, and it is assumed that is accessible via http using your own web browser. This is working for me. However, I had to hack getting the directory location to the challenge provider, and of course the project files are now different. I am not sure that my total changes would be suitable for a general release, but am happy to share them. If anyone has thoughts on how to do this, please suggest away! It isn't worth a fork as I can't do the wider maintenance.
up
There are other solutions which are actively maintained. I have not worked on this project for years.
Out of curiosity, is there anything that this project can do that other solutions don't have, or why are you asking for a new release?
I am trying to package this solution for Gentoo Linux system. Because I am fun of C# and gentoo. Other solutions are either not C# or doesn't work for me. I need some tag by rules for writing ebuild scripts. I can, of course, use SHA1, but that will be a bit worse.
There are other solutions which are actively maintained.
May I ask you to name them?
UPD: on the page https://letsencrypt.org/docs/client-options/ fszlin/Certes (.NET Standard) PKISharp/ACMESharpCore (.NET Standard)
Yes. Did you try one of these?
Personally, I don't handle certificates myself anymore. I've just put my site behind a CDN. Cloudflare provides everything I need for free.
Hi can someone rebuild the project with the new terms and conditions and submit it as a release.
Thank you