Skip to content
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.

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

Unprotect-PGP paramset can't be resolved if there is no password/credential #4

Closed
Szeraax opened this issue Sep 16, 2021 · 2 comments
Closed
Labels
bug Something isn't working

Comments

@Szeraax
Copy link

Szeraax commented Sep 16, 2021

As stated, if you use a PGP key that has no passphrase to use it, the cmdlet errors with this message:

 Unprotect-PGP : Parameter set cannot be resolved using the specified named parameters.

Probably just need to add in another parameter set for file/folder decryption that doesn't take either.

@PrzemyslawKlys PrzemyslawKlys added the bug Something isn't working label Sep 16, 2021
@PrzemyslawKlys
Copy link
Member

I wasn't aware you can use the PGP key without a password. This needs fixing. Feel free to submit PR, otherwise I'll do it at some point.

@mchassy
Copy link

mchassy commented May 11, 2023

Is there anything to be done once I have created my keys without a password? I have moved from a windows machine to a mac. On the windows machine I used the powershell commanlets and pointed to the private key files. On the mac, I can still do that with powershell for mac. But if I try using bash scripts using gpg commands, I am asked to give the password. Can I modfy my keys to add a password using the comandlets?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants