8000 Get-pfxCertificate cmdlet not working · Issue #473 · PowerShell/PowerShell · GitHub
[go: up one dir, main page]
Skip to content

Get-pfxCertificate cmdlet not working #473

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
Closed
palladia opened this issue Feb 2, 2016 · 9 comments
Closed

Get-pfxCertificate cmdlet not working #473

palladia opened this issue Feb 2, 2016 · 9 comments
Labels
OS-Linux OS-macOS Resolution-Fixed The issue is fixed. WG-Cmdlets general cmdlet issues

Comments

@palladia
Copy link
Contributor
palladia commented Feb 2, 2016

No description provided.

@palladia palladia added this to the Preview 1 milestone Feb 2, 2016
@andyleejordan
Copy link
Member

This would not make sense, PFX certificates are only used on Windows.

@andyleejordan andyleejordan removed this from the Preview 1 milestone Feb 3, 2016
@palladia
Copy link
Contributor Author
palladia commented Feb 3, 2016

I am certainly not an expert on certificates, but just because it's a Windows thing, it doesn't mean it shouldn't be implemented on Linux. Certificates are basically wrappers for public keys, and are there 8000 alternate mechanisms for Linux? What happens if we need to inter-work between Linux and Windows?

I hope whoever gets assigned to this can investigate this further.

@andyleejordan
Copy link
Member

I do not think this should be implemented on Linux. The cmdlet is meant to return the PFX certificates stored on the system, of which there are and will not be any on Linux.

@bgever
Copy link
bgever commented May 6, 2017

PFX is a very common certificate encapsulation format, many online services support it to pass certificate structures around that are password protected.

It's also the default way to support HTTPS with the Kestrel server in .NET Core 1.1.

Therefore I think PFX support shouldn't be dismissed. I did see that with release v6.0.0-alpha.17 #3224 the Get-PfxCertificate is now supported. 👍

@PsychoData
Copy link

Just to add to this, there is also a -FIlePath to import from a file
Get-PfxCertificate -FilePath $certFile

Which I am using to then check the thumbprint of that certificate without importing it into my windows store, this use case could be equally useful on Linuxes.

@iSazonov
Copy link
Collaborator

@SteveL-MSFT Should we re-open this for Unix?

@SteveL-MSFT SteveL-MSFT added the WG-Cmdlets general cmdlet issues label Jun 11, 2017
@SteveL-MSFT SteveL-MSFT reopened this Jun 11, 2017
@SteveL-MSFT
Copy link
Member

We'll need to do more research on PowerShell cert management on Linux, but this currently is not a priority.

@iSazonov
Copy link
Collaborator

I think OpenSSL utilities is good start point for the research.

@Karneades Karneades mentioned this issue Aug 10, 2017
Closed
@iSazonov
Copy link
Collaborator
iSazonov commented Oct 7, 2017

Get-PfxCertificate was added in #3224 for Windows and Unix.
What do we track here? Maybe close?

@SteveL-MSFT SteveL-MSFT added the Resolution-Fixed The issue is fixed. label Oct 8, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
OS-Linux OS-macOS Resolution-Fixed The issue is fixed. WG-Cmdlets general cmdlet issues
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@bgever @andyleejordan @PsychoData @SteveL-MSFT @palladia @iSazonov
0