McMaster.AspNetCore.LetsEncrypt 0.2.0

The ID prefix of this package has been reserved for one of the owners of this package by NuGet.org. Prefix Reserved
.NET Core 3.0 .NET Standard 2.0
Suggested Alternatives

LettuceEncrypt

Additional Details

Package renamed to LettuceEncrypt. See https://github.com/natemcmaster/LettuceEncrypt/issues/99 for details

The owner has unlisted this package. This could mean that the package is deprecated, has security vulnerabilities or shouldn't be used anymore. 
dotnet add package McMaster.AspNetCore.LetsEncrypt --version 0.2.0
NuGet\Install-Package McMaster.AspNetCore.LetsEncrypt -Version 0.2.0
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package. 
<PackageReference Include="McMaster.AspNetCore.LetsEncrypt" Version="0.2.0" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
paket add McMaster.AspNetCore.LetsEncrypt --version 0.2.0
#r "nuget: McMaster.AspNetCore.LetsEncrypt, 0.2.0"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package. 
// Install McMaster.AspNetCore.LetsEncrypt as a Cake Addin
#addin nuget:?package=McMaster.AspNetCore.LetsEncrypt&version=0.2.0

// Install McMaster.AspNetCore.LetsEncrypt as a Cake Tool
#tool nuget:?package=McMaster.AspNetCore.LetsEncrypt&version=0.2.0

Provides API for configuring ASP.NET Core to use Let's Encrypt.org to automaticaly generate HTTPS certificates.

Let's Encrypt is a free, automated, and open Certificate Authority. When this package is installed and enabled, your web server will
use the Let's Encrypt certificate authority and automatically generate an HTTPS certificate when the server starts up.
It then configures Kestrel to use this certificate for all HTTPS traffic.

This only works with Kestrel, which is the default server configuration for ASP.NET Core projects. Other servers, such as IIS and nginx, are not supported.
   

This package was build from source code at https://github.com/natemcmaster/LetsEncrypt/tree/dd50747ef7bd735674a98850e292f9c894b36d71

Product Compatible and additional computed target framework versions.
.NET net5.0 was computed.  net5.0-windows was computed.  net6.0 was computed.  net6.0-android was computed.  net6.0-ios was computed.  net6.0-maccatalyst was computed.  net6.0-macos was computed.  net6.0-tvos was computed.  net6.0-windows was computed.  net7.0 was computed.  net7.0-android was computed.  net7.0-ios was computed.  net7.0-maccatalyst was computed.  net7.0-macos was computed.  net7.0-tvos was computed.  net7.0-windows was computed.  net8.0 was computed.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed. 
.NET Core netcoreapp2.0 was computed.  netcoreapp2.1 was computed.  netcoreapp2.2 was computed.  netcoreapp3.0 is compatible.  netcoreapp3.1 was computed. 
.NET Standard netstandard2.0 is compatible.  netstandard2.1 was computed. 
.NET Framework net461 was computed.  net462 was computed.  net463 was computed.  net47 was computed.  net471 was computed.  net472 was computed.  net48 was computed.  net481 was computed. 
MonoAndroid monoandroid was computed. 
MonoMac monomac was computed. 
MonoTouch monotouch was computed. 
Tizen tizen40 was computed.  tizen60 was computed. 
Xamarin.iOS xamarinios was computed. 
Xamarin.Mac xamarinmac was computed. 
Xamarin.TVOS xamarintvos was computed. 
Xamarin.WatchOS xamarinwatchos was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated

Important update! LetsEncrypt.org is deprecating v1 of their protocol, which earlier versions of this package used.
You should update to 0.2.0 soon to avoid interruption to your ability to automaticaly provision HTTPS certs.

Special thanks to Michal Bičan (@mbican) for updating this package to use the ACME v2 protocol.

Features:
* @mbican: add API for configuring the private key algorithm (#20)
* @mbican: update to use ACME v2 protocol (#23)

Bug fixes:

* Fix #19 - handle HTTPS requests that don't have a domain name
* Don't try to load certificates when using IIS out-of-process hosting.