- Sep 14, 2013
-
-
Brian Shore authored
-
- May 22, 2013
-
-
Brian Mattern authored
-
- Apr 04, 2013
-
-
Jason A. Donenfeld authored
-
- Feb 23, 2013
-
-
Marvin Killing authored
Make show/ls/list follow links by passing -l to tree.
-
- Oct 18, 2012
-
-
Jason A. Donenfeld authored
-
- Oct 16, 2012
-
-
guns authored
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.
-
- Oct 09, 2012
-
-
Jason A. Donenfeld authored
-
- Oct 05, 2012
-
-
Jason A. Donenfeld authored
-
- Oct 03, 2012
-
-
Jason A. Donenfeld authored
Reported-by:
Paul Wise <pabs@debian.org>
-
- Sep 30, 2012
-
-
Jason A. Donenfeld authored
- Sep 23, 2012
-
-
Jason A. Donenfeld authored
-
Jonathan Chu authored
Redefine GNUPG and GETOPT for port paths Redefine tmpdir() for a different ramdisk path
- Sep 22, 2012
-
-
Jason A. Donenfeld authored
-
Jason A. Donenfeld authored
-
Jason A. Donenfeld authored
-
Jason A. Donenfeld authored
-
Jason A. Donenfeld authored
-
Jason A. Donenfeld authored
-
- Sep 21, 2012
-
-
Jason A. Donenfeld authored
-
Jason A. Donenfeld authored
Reported-by:
Simon KP <si@eskp.net>
-
- Sep 20, 2012
-
-
Jason A. Donenfeld authored
Reported-by:
Brian Mattern <rephorm@rephorm.com>
-
Jason A. Donenfeld authored
-
- Sep 19, 2012
-
-
Jason A. Donenfeld authored
-
Jason A. Donenfeld authored
-
Jason A. Donenfeld authored
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.
-
Jason A. Donenfeld authored
-
- Sep 18, 2012
-
-
Jason A. Donenfeld authored
-
- Sep 17, 2012
-
-
Jason A. Donenfeld authored
-
Jason A. Donenfeld authored
-
- Sep 16, 2012
-
-
Jason A. Donenfeld authored
Laurent asked for this. Reported-by:
Laurent Ghigonis <laurent@p1sec.com>
-
Jason A. Donenfeld authored
Reported-by:
Laurent Ghigonis <laurent@p1sec.com>
-
- Sep 14, 2012
-
- Sep 13, 2012
-
-
Jason A. Donenfeld authored
-
Jason A. Donenfeld authored
-
Jason A. Donenfeld authored
Reported-by:
Brian Mattern <rephorm@rephorm.com>
-
Brian Mattern authored
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.
-
Brian Mattern authored
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.
-