| Age | Commit message (Collapse) | Author |
|---|
|
This is required by most graphical editors, as the shell command they
provide needs to be told to wait until the file has been closed.
This reverts '311c98c9140205f32be2720db9261c67da658c4c'. We thus use
PATH so that the tests still pass in directories with spaces.
|
|
|
|
|
|
|
|
Key discovery parses stderr output of gnupg. The secmem warning
interferes with parsing.
|
|
|
|
|
|
|
|
- usefull for git commands showing diff, e.g.: pass git log -p
- from what I can see, not 'cleartext' temporary files are created
|
|
|
|
|
|
|
|
Revert "Mute git-commit messages to make pass insert readable"
This reverts commit f30ce6374d554e704162d5fa8e49acd9c6fd0ecc.
I decided I like the git output. Instead highlight generated passwords
using nice terminal output instead.
|
|
This reverts commit 56381287a16792b4c6410f07db68e02f3574c213, and
further fixes things.
|
|
|
|
|
|
`pass generate' prints 10 lines of output, with only 2 related
to the operation at hand:
% pass generate xyz
1
2 You need a passphrase to unlock the secret key for
3 user: USER <EMAIL>
4 4096-bit RSA key, ID XYZ, created 1234-56-78
5
6 [master 12345] Added generated password for xyz to store.
7 1 file changed, 0 insertions(+), 0 deletions(-)
8 create mode 100644 xyz.gpg
9 The generated password to xyz is:
10 Some password 123
%
This patch takes care of 3 of 8 noise lines.
|
|
Made sed expression GNU and BSD compatible.
A recent change in pass.zsh-completion broke autocompletion when using
BSD sed. I’ve made the relevant sed expression compatible with GNU and
BSD sed.
Previous change with regression:
http://lists.zx2c4.com/pipermail/password-store/2014-April/000773.html
http://git.zx2c4.com/password-store/commit/src/completion/pass.zsh-completion?id=f82e9d6cf3bc3a12bdfce89bf319d76f79e66efc
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
|
|
From Kevin:
I found a small bug in the zsh completions. Basically when the
PASSWORD_STORE_DIR ends in a slash the first character of the
result is eaten, making completion essentially useless. (It does
this before determining matches).
This can be fixed by changing what is line 106 in my version from:
_values -C 'passwords' $(find -L "$prefix" \( -name .git -o -name
.gpg-id \) -prune -o $@ -print | sed -e "s#${prefix}.##" -e 's#\.gpg##'
| sort)
to
_values -C 'passwords' $(find -L "$prefix" \( -name .git -o -name
.gpg-id \) -prune -o $@ -print | sed -e "s#${prefix}/\\?##" -e
's#\.gpg##' | sort)
The difference is the first sed regex expression. The original
version assumed that the next character was a slash and removed
it while the new version only removes it if it is a slash.
"s#${prefix}.##" -> "s#${prefix}/\\?##"
Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
Reported-by: Kevin Cox <kevincox@kevincox.ca>
|
|
|
|
|
|
|
|
|
|
In fact, if we're running from the source directory, just auto-detect
the platform file in the first place.
Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
|
|
The new environment variable, PASSWORD_STORE_PLATFORM_FILE is now used
for loading custom platform files while pass lives as
src/password-store.sh. After it is installed using 'make install', this
environment variable is no longer used, and either no platform file is
loaded (if the default platform is acceptable), or a hardcoded
also-installed platform file is referenced.
Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
|
|
|
|
|
|
|