diff options
author | Jason A. Donenfeld <Jason@zx2c4.com> | 2012-09-12 02:05:53 +0200 |
---|---|---|
committer | Jason A. Donenfeld <Jason@zx2c4.com> | 2012-09-12 02:05:53 +0200 |
commit | 6ecdfe3844eec6e3d3f2d04c506c75114d97a5ec (patch) | |
tree | d52e674a1dd3cb2e1a61cd6ddb6d35e1dad6413d /man/pass.1 | |
parent | f423a27d4da8a1b830e368d846880886470b22dd (diff) | |
download | pass-6ecdfe3844eec6e3d3f2d04c506c75114d97a5ec.tar.gz pass-6ecdfe3844eec6e3d3f2d04c506c75114d97a5ec.tar.bz2 pass-6ecdfe3844eec6e3d3f2d04c506c75114d97a5ec.zip |
Use PASSWORD_STORE_DIR environment variable if it is set.
A user made this request:
I was wondering whether it is in a planning to have multiple
password-store directory trees or possible to achieve? eg.
$HOME/.pwd-store-work and $HOME/.pwd-store-home. Maybe distinguish them
with a command line switch and then create aliases in .bash_aliases?
Why I'm asking is that I have multiple major password categories -
personal, work etc. It'll be nice to keep them separate and under
different repos.
Reported-by: Simon KP <si@eskp.net>
Diffstat (limited to 'man/pass.1')
-rw-r--r-- | man/pass.1 | 7 |
1 files changed, 4 insertions, 3 deletions
@@ -19,7 +19,8 @@ pass - stores, retrieves, generates, and synchronizes passwords securely is a very simple password store that keeps passwords inside .BR gpg (1) encrypted files inside a simple directory tree residing at -.IR $HOME/.password-store . +.IR $HOME/.password-store , +or the environment variable \fBPASSWORD_STORE_DIR\fP if it is set. The .B pass utility provides a series of commands for manipulating the password store, @@ -82,8 +83,8 @@ Insert a new password or edit an existing password using the default text editor by the environment variable \fBEDITOR\fP or using .BR vi (1) as a fallback. This mode makes use of temporary files for editing, but care is taken to -ensure that temporary files are created in \fB/dev/shm\fP in order to avoid writing to -difficult-to-erase disk sectors. If \fB/dev/shm\fP is not accessible, fallback to +ensure that temporary files are created in \fI/dev/shm\fP in order to avoid writing to +difficult-to-erase disk sectors. If \fI/dev/shm\fP is not accessible, fallback to the ordinary \fBTMPDIR\fP location, and print a warning. .TP \fBgenerate\fP [ \fI--no-symbols\fP, \fI-n\fP ] [ \fI--clip\fP, \fI-c\fP ] \fIpass-name pass-length\fP |