m-chrzan.xyz
aboutsummaryrefslogtreecommitdiff
path: root/tests/gnupg/private-keys-v1.d/C93F70CA322D4F42E7FC7D54F6367E65C23E5CA3.key
diff options
context:
space:
mode:
authorBrian Mattern <rephorm@rephorm.com>2012-09-12 22:25:20 -0700
committerJason A. Donenfeld <Jason@zx2c4.com>2012-09-13 08:04:17 +0200
commit69b811e0f34a2f57329e5cdfebcd16c210f24458 (patch)
treed0e02addf655f3ff1c7e7a5521ebd7a79723fc39 /tests/gnupg/private-keys-v1.d/C93F70CA322D4F42E7FC7D54F6367E65C23E5CA3.key
parent36a453ed91407dec1bb2215e0a871d23c0645305 (diff)
use gpg --batch for quieter output
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.
Diffstat (limited to 'tests/gnupg/private-keys-v1.d/C93F70CA322D4F42E7FC7D54F6367E65C23E5CA3.key')
0 files changed, 0 insertions, 0 deletions