New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Consider replacing Certes #24

Open

TCFox opened this issue Feb 3, 2020 · 0 comments

Labels

Member

TCFox commented Feb 3, 2020

Would solve the following issues:

Support setting OCSP Must-Staple in ACME request #23 (Support OCSP Must-Staple in certificates)
Use Azure Key Vault Keys to store ACME account key #7 (Store ACME key as non-exportable Key Vault Key)

Would also allow us to:

Replace BouncyCastle with Key Vault operations and .NET Core 3.0 functions
Generate ACME account private keys entirely within Key Vault Keys (no risk of keys leaking)
Generate certificate private keys entirely within Key Vault Certificates too

Certes might be a good start so it may be worth forking https://github.com/fszlin/certes and stripping it down to just what we need.

TCFox added the enhancement label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment