You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Encrypting a file to the password store via path expansion of $PASSWORD_STORE_DIR, creates a directory structure of the expanded path from password store dir root.
This is certainly not intentional but I wonder if it's worth a workaround. I think you're using gopass wrong. Neither input nor output should contain $PASSWORD_STORE_DIR. In fact you should usually not mess with the contents directly (or at least not using gopass to target anything in there).
Summary
Encrypting a file to the password store via path expansion of $PASSWORD_STORE_DIR, creates a directory structure of the expanded path from password store dir root.
Steps To Reproduce
Results (on mac) in:
$PASSWORD_STORE_DIR/Users/<user>/path/to/password-store/test-file.txt.gpg
i.e.,$PASSWORD_STORE_DIR/Users/<user>/$PASSWORD_STORE_DIR/test-file.txt.gpg
Expected behavior
Creates an encrypted file of
~/test-file.txt
at$PASSWORD_STORE_DIR
root. i.e.,$PASSWORD_STORE_DIR/test-file.txt.gpg
Environment
Additional context
Additionally, it would be great if gopass could also handle an empty target filename.
e.g:
gopass fscopy ./test-file.txt $PASSWORD_STORE_DIR
should result in a file namedtest-file.txt.gpg
at$PASSWORD_STORE_DIR
.Currently what happens is similar as the behaviour as above, but the password store root folder is used as the file name.
$PASSWORD_STORE_DIR/Users/<user>/path/to/password-store/password-store-folder-root-name.gpg
The text was updated successfully, but these errors were encountered: