-
Notifications
You must be signed in to change notification settings - Fork 23
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
Get-Secret fails to retrieve some secrets listed by Get-SecretInfo #63
Comments
Repro'ed with SecretManagement.KeePass version 0.9.2 |
Try it with verbose and debug turned on? There might be some clues in there. |
|
Sounds like something went null somewhere. If you can make a dummy keepass file that you can reproduce the issue I can debug it and find what's going wrong. |
Here you go: test.zip Master password is
|
@sba923: It looks like a similar issue I run into. If you do store an item in Keepass with no (or empty) password, SecretManagement.KeePass would internally return a null-value. This finally seems to be treated as "no secret found" by MS.SecretManagement. IMHO this is OK. Because afiak the SecretManagement module would generally not allow to set "empty" secrects. |
@danubie thanks for sharing your thoughts I actually use KeePass to store all kinds of secrets, some of which have an empty "Username" field and/or an empty "Password" field, for instance for software product keys, phone IMEIs.... |
That's exactly where I got caught: A folder for API keys having "usernames" but no password |
Hi, I just put the API key in the password and a "1" for the username |
This should speak for itself:
In the affected vault,
Get-SecretInfo
lists 85 secrets, this failure occurs for 8 of them:I'm running PowerShell 7.1.4 on Windows 10.0.19043.1165.amd64fre.vb_release.191206-1406 with Microsoft.PowerShell.SecretManagement version 1.1.0 and SecretManagement.KeePass version 0.9.1.3
The text was updated successfully, but these errors were encountered: