search

PKISolutions / PSPKI

PowerShell PKI Module
Microsoft Public License
378 stars 57 forks source link

Feature Request: Add function New-CertificateSigningRequestEx #78

Open PatrickOnGit opened 5 years ago

PatrickOnGit commented 5 years ago

The function New-SelfSignedCertificateEx does not allow for creating CSRs. Neither does the SysadminsLV.PKI.Cryptography.X509Certificate.X509CertificateBuilder class. So it would be great to have this function.

Crypt32 commented 5 years ago

Next two months I will be very busy, but I will put this in my ToDo list.

I think, there will be two versions: 1) cross-platform with PKCS#1/PKCS#8 key storage (similar to OpenSSL). I know, there is CertificateRequest class in .NET 4.7.2 and .NET core, but I think, it is not flexible. 2) Microsoft-specific that will utilize windows certificate store.

If you have other ideas, drop them in this thread.

PatrickOnGit commented 5 years ago

Hello Vadims

This sounds great. Thank you. For PKCS#1/PKCS#8 key storage you might allow for encrypted and unencrypted PEM-key.

What I'm also looking for is an option to sign CSR with a RA Agent certificate.

Using PowerShells capability for dynamic parameters, it would be kind of cool if the commands would allow for tab completion for available Provider and Algorithm types etc. Your command Get-CryptographicServiceProvider already reveals this information.

Thank you Kind regards Patrick

Von: Vadims Podans notifications@github.com Gesendet: Mittwoch, 1. Mai 2019 15:24 An: Crypt32/PSPKI Cc: PatrickOnGit; Author Betreff: Re: [Crypt32/PSPKI] Feature Request: Add function New-CertificateSigningRequestEx (#78)

Next two months I will be very busy, but I will put this in my ToDo list.

I think, there will be two versions:

cross-platform with PKCS#1/PKCS#8 key storage (similar to OpenSSL). I know, there is CertificateRequest class in .NET 4.7.2 and .NET core, but I think, it is not flexible. Microsoft-specific that will utilize windows certificate store.

If you have other ideas, drop them in this thread.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

PatrickOnGit commented 4 years ago

is there a plan to work on this request?

Crypt32 commented 4 years ago

Yes, I'm considering this as well. In next version, I'm going to revisit existing GitHub items and work on them.

PatrickOnGit commented 4 years ago

thank you