summaryrefslogtreecommitdiff
path: root/src (follow)
Commit message (Collapse)AuthorAgeFilesLines
...
* Do not compress passwords.Jason A. Donenfeld2014-03-181-1/+1
| | | | | | | | | | | According to a forthcoming paper by Alfredo Pironti, OpenPGP compression can reveal entropy levels. We thus disable compression. Existing password stores can be reencrypted without compression using the "--reencrypt" flag for "init". Reported-by: Alfredo Pironti <alfredo.pironti@inria.fr> Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
* Use a glob in the pattern match instead of using two comparisons for [yY].Chris Down2013-09-141-1/+1
|
* Rephrase awkward/confusing message about enabling echo during password entry.Chris Down2013-09-141-3/+3
|
* Fix directory traversal for reencryption when $PREFIX is a symlinkBrian Shore2013-09-141-1/+1
|
* check if a passfile exists before checking for directoryBrian Mattern2013-05-221-13/+12
|
* Simplify sed to not use replacement.Jason A. Donenfeld2013-04-041-1/+1
|
* Tree should follow symlinks.Marvin Killing2013-02-231-1/+1
| | | | Make show/ls/list follow links by passing -l to tree.
* Bump version.Jason A. Donenfeld2012-10-181-1/+1
|
* Do not interpret backslashes when reading passwordsguns2012-10-171-4/+4
| | | | | | | | | | | | | | | | | The `read` builtin accepts backslash notation for common non-printing characters by default, like `\t` and `\n`. This requires that any literal backslashes must also be escaped as `\\`. Given that `gpg -e` does not interpret input, the `read` invocations are changed to do the same. Also, the right hand side of an `==` comparison within `[[ ]]` must be quoted in order to suppress pattern metacharacter expansion. Quoting the bash manual: When the == and != operators are used, the string to the right of the operator is considered a pattern and matched according to the rules described below under Pattern Matching.
* Restore exclusivity of options in multiline/echo check.Jason A. Donenfeld2012-10-091-1/+1
|
* Trim trailing slash in tree display.Jason A. Donenfeld2012-10-051-1/+1
|
* Make --no-echo default, and rename to --echo.Jason A. Donenfeld2012-10-031-8/+8
| | | | Reported-by: Paul Wise <pabs@debian.org>
* Check error code of gpg before copying to clipboard.1.4.1Jason A. Donenfeld2012-09-301-1/+3
|
* Explicitly use gpg2 rather than relying on symlink.Jason A. Donenfeld2012-09-303-12/+9
|
* Style fixes.1.4Jason A. Donenfeld2012-09-241-1/+2
|
* Fix style.Jason A. Donenfeld2012-09-231-11/+9
|
* Add FreeBSD platform fileJonathan Chu2012-09-231-0/+21
| | | | | Redefine GNUPG and GETOPT for port paths Redefine tmpdir() for a different ramdisk path
* Normalize negation and bashism.Jason A. Donenfeld2012-09-221-7/+7
|
* Fix directory removal.Jason A. Donenfeld2012-09-221-5/+8
|
* Add man page comment to usage message.Jason A. Donenfeld2012-09-221-0/+2
|
* Bump version to 1.4.Jason A. Donenfeld2012-09-221-1/+1
|
* Normalize copyright headers.Jason A. Donenfeld2012-09-222-2/+5
|
* Allow git repo to be elsewhere via env var.Jason A. Donenfeld2012-09-221-2/+2
|
* Add support for PASSWORD_STORE_KEY env var.Jason A. Donenfeld2012-09-211-1/+3
|
* Add option to init to reencrypt all passwords.Jason A. Donenfeld2012-09-211-2/+22
| | | | Reported-by: Simon KP <si@eskp.net>
* Quit if pwgen returns nothing.Jason A. Donenfeld2012-09-201-0/+1
| | | | Reported-by: Brian Mattern <rephorm@rephorm.com>
* Prompt before overwriting password in generate, unless --force is provided.Jason A. Donenfeld2012-09-201-21/+23
|
* Make qdbus ugliness more segmented.Jason A. Donenfeld2012-09-191-3/+8
|
* Since we're using batch mode, we can read directly.Jason A. Donenfeld2012-09-191-1/+1
|
* Clean up git handling.Jason A. Donenfeld2012-09-191-29/+17
| | | | | | Get rid of push/pull shortcuts, as they weren't widely used. Add contents to repo on git init. Centralize git add logic, and make it less error prone.
* Fix git regression.Jason A. Donenfeld2012-09-191-1/+1
|
* Quote the template.Jason A. Donenfeld2012-09-181-1/+1
|
* Quote the program name.Jason A. Donenfeld2012-09-181-4/+4
|
* Abstract potentially platform specific commands into their own commands.Jason A. Donenfeld2012-09-172-33/+82
|
* Support recursive and forced removal.Jason A. Donenfeld2012-09-161-10/+24
| | | | | | Laurent asked for this. Reported-by: Laurent Ghigonis <laurent@p1sec.com>
* Small stylistic things.Jason A. Donenfeld2012-09-161-9/+9
| | | | Reported-by: Laurent Ghigonis <laurent@p1sec.com>
* Bump to 1.3.1.1.3.1Jason A. Donenfeld2012-09-141-1/+1
|
* Typo.Jason A. Donenfeld2012-09-131-1/+1
|
* Bump version.1.3Jason A. Donenfeld2012-09-131-1/+1
|
* Allow avoiding the prompt for overwriting, with --force flag.Jason A. Donenfeld2012-09-131-5/+8
|
* Split out common gpg options into variable.Jason A. Donenfeld2012-09-131-6/+7
| | | | Reported-by: Brian Mattern <rephorm@rephorm.com>
* use gpg --batch for quieter outputBrian Mattern2012-09-131-3/+3
| | | | | | | | | | | | | | Right now, every time I call pass to decrypt a key, I get output like: You need a passphrase to unlock the secret key for user: "User Name <user@domain.com>" 2048-bit ELG-E key, ID XXXXXXNX, created 2012-04-20 (main key ID NNXXNNNX) password This patch cleans it up so that only the password is output. I use pinentry-gtk-2 to enter the gpg passphrase, so this information is redundant to me. I haven't tried other pinentry versions to see if they repeat the information as well.
* prevent <ctrl-c> on password entry from wiping out fileBrian Mattern2012-09-131-2/+2
| | | | | | | | | | | | | Currently, if you hit ctrl-c at the standard 'Enter password' prompt, since it is piped directly to gpg, the entry gets cleared. Trying to read from that entry results in: gpg: [don't know]: 1st length byte missing This patch fixes this. Tweaked by Jason A. Donenfeld <Jason@zx2c4.com> to add GNU readline features by using -e in read.
* Confirm before overwriting an entryBrian Mattern2012-09-131-1/+8
| | | | | This asks before inserting a password when one already exists at that location (instead of just overwriting it).
* Use bash's read command better.Jason A. Donenfeld2012-09-131-14/+8
|
* Add --version switch, per request.Jason A. Donenfeld2012-09-131-4/+20
|
* Be more careful about cleaning up.Jason A. Donenfeld2012-09-131-6/+4
|
* Use getopt to regularize optionsBrian Mattern2012-09-121-27/+35
| | | | | | | | | I like being able to specify command line options (like -c) at the end of the line (which is usually when I think of the fact that I need them). The attached patch uses getopt(1) to regularize the option list so that lazy people like me can specify the options in any order.
* Don't quote ${EDITOR:-vi}rupa2012-09-121-1/+1
| | | | | | | | Attached is a trivial patch that removes the quotes from the line that invokes $EDITOR. It's perfectly cromulent to set $EDITOR to something with spaces in it, so when we evaluate this one we want it evaluated bare. For example security nerds might want EDITOR='vim -n' if they are scared of swap files, and that breaks if we quote there.
* Use PASSWORD_STORE_DIR environment variable if it is set.Jason A. Donenfeld2012-09-121-1/+1
| | | | | | | | | | | | | | | 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>