Unlock-SecretStore not working when using Remote-SSH connection in VsCode #89

Activity

1. Paul Higinbotham (PaulHigin)

   transferred this issue fromPowerShell/SecretManagementon Dec 9, 2021
2. PaulHigin commented on Dec 9, 2021

   

   Paul Higinbotham (PaulHigin)

   on Dec 9, 2021

   Contributor

   More actions

   This sounds like it might be related to issue #62, which has to do with how SecretStore encrypts one layer using the current user account name. Windows can provide the user name in different cases, and this affects the ability to decrypt. The problem has been fixed in the latest version of SecretStore. What version are you using?

   Keep in mind that SecretStore currently stores secrets for the current user account. 'AllUser' scope is not yet supported, so to access secrets means logging in with the account that stored the secrets.
3. dillardd commented on Dec 21, 2021

   

   dillardd

   on Dec 21, 2021

   Last edited by dillardd

   Author

   More actions

   I think this is related to issue #62 , as I am not getting an error:

   Padding is invalid and cannot be removed

   I received this after updating the modules to latest versions:

   ModuleType Version    PreRelease Name                                PSEdition ExportedCommands
   ---------- -------    ---------- ----                                --------- ----------------
   Binary     1.1.1                 Microsoft.PowerShell.SecretManagem… Core      {Register-SecretVault, Unregister-SecretVault, Get-SecretVault, Set-SecretVaultDefault…}
   Binary     1.0.5                 Microsoft.PowerShell.SecretStore    Core      {Unlock-SecretStore, Set-SecretStorePassword, Get-SecretStoreConfiguration, Set-SecretStoreConfiguration…}
   

   I am logged in as the same user via the Remote-SSH session, so it shouldn't be an issue of 'AllUser' scope, but I definitely understand what you mean about Windows not presenting the user in a fashion that the Module is able to decrypt.

   I would say the issues could be merged, however #62 looks like it is closed.
4. PaulHigin commented on Jan 3, 2022

   

   Paul Higinbotham (PaulHigin)

   on Jan 3, 2022

   Contributor

   More actions

   Yes, the issue #62 has been fixed, but there is a chance that if you have a SecretStore database from before the fix, you will see this error. That is why I recommended to original author of #62 to reset and re-store secrets after installing the latest SecretStore with the fix.

   There is a small chance that you may have older versions of the module. Please run:

   Get-module -Name Microsoft.PowerShell.Secret* -list

   to ensure any older versions have been removed.
5. dillardd commented on Jan 5, 2022

   

   dillardd

   on Jan 5, 2022

   Author

   More actions

   When running the command to get the installed versions of the Module, this is what I get. There aren't older versions, but there are versions installed into multiple folders:

   Get-module -Name Microsoft.PowerShell.Secret* -list
   
       Directory: C:\Users\Administrator\Documents\PowerShell\Modules
   
   ModuleType Version    PreRelease Name                                PSEdition ExportedCommands
   ---------- -------    ---------- ----                                --------- ----------------
   Binary     1.1.1                 Microsoft.PowerShell.SecretManagem… Core      {Register-SecretVault, Unregister-SecretVault, Get-SecretVault, Se…
   Binary     1.0.5                 Microsoft.PowerShell.SecretStore    Core      {Unlock-SecretStore, Set-SecretStorePassword, Get-SecretStoreConfi…
   
       Directory: C:\Program Files\WindowsPowerShell\Modules
   
   ModuleType Version    PreRelease Name                                PSEdition ExportedCommands
   ---------- -------    ---------- ----                                --------- ----------------
   Binary     1.1.1                 Microsoft.PowerShell.SecretManagem… Core      {Register-SecretVault, Unregister-SecretVault, Get-SecretVault, Se…
   Binary     1.0.5                 Microsoft.PowerShell.SecretStore    Core      {Unlock-SecretStore, Set-SecretStorePassword, Get-SecretStoreConfi…
   

   I started getting the error Padding is invalid and cannot be removed today, and it affected many scripts that I had running in Task Scheduler. After entering in the credentials again for one task, all of the others that used that account started working, however they stopped working again a couple of hours later.

   I am going to take your advice and recreate the secret store, which I imagine will remedy this situation since it is now manifesting in exactly the way described in #62 .

   I appreciate your attention to this and will update again.

   👍React with 👍1Reacted by Paul Higinbotham