From: Valentin Reis <valentin.reis@gmail.com>
To: supmua <supmua@googlegroups.com>
Subject: gpg-agent issue
Date: Tue, 17 Mar 2015 13:49:19 +0100 [thread overview]
Message-ID: <1426596032-sup-4861@frex230> (raw)
Hello,
Sup asks for my gpg passphrase every time it has to encrypt, sign or
decrypt an e-mail, even though I am using gpg-agent.
When decrypting files sequentially using gpg or gpg2, gpg-agent is used,
and I have to provide the passphrase just once.
Here are the contents of my config files:
.gnupg/gpg.conf
keyserver hkp://keys.gnupg.net
use-agent
.gnupg/gpg-agent.conf
pinentry-program /usr/bin/pinentry-curses
.sup/config.yaml
...
:accounts:
:default:
...
:gpgkey: 59EA13A1
...
No crypto hooks in .sup/hooks are in use.
gpg --list-keys
/home/fre/.gnupg/pubring.gpg
----------------------------
pub 2048R/59EA13A1 2014-04-28
uid Valentin Reis <valentin.reis@gmail.com>
sub 2048R/C8DA9D35 2014-04-28
sub 2048R/4F728EEB 2014-04-28
It is a debian machine. Various apt-get output:
gnupg-agent is already the newest version.
libgpgme11 is already the newest version.
gnupg2 is already the newest version.
Cheers!
val
--
next reply other threads:[~2015-03-17 12:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-17 12:49 Valentin Reis [this message]
2015-03-17 12:51 ` valentin.reis
2015-03-17 13:31 ` [sup] " Johannes Larsen
2015-03-17 13:33 ` Valentin Reis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1426596032-sup-4861@frex230 \
--to=valentin.reis@gmail.com \
--cc=supmua@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox