From: "valentin.reis" <valentin.reis@gmail.com>
To: supmua@googlegroups.com
Subject: Re: gpg-agent issue
Date: Tue, 17 Mar 2015 05:51:46 -0700 (PDT) [thread overview]
Message-ID: <48037a62-3da5-4a29-bd79-6dd1feb61879@googlegroups.com> (raw)
In-Reply-To: <1426596032-sup-4861@frex230>
[-- Attachment #1.1: Type: text/plain, Size: 1314 bytes --]
In case this is not clear, I would like sup to use gpg-agent correctly, so
as not to have to enter my passphrase repeatedly.
Do any of you see something I'm doing wrong?
Thanks!
On Tuesday, 17 March 2015 13:49:24 UTC+1, valentin.reis wrote:
>
> 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
>
> --
>
[-- Attachment #1.2: Type: text/html, Size: 2232 bytes --]
next prev parent reply other threads:[~2015-03-17 12:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-17 12:49 Valentin Reis
2015-03-17 12:51 ` valentin.reis [this message]
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=48037a62-3da5-4a29-bd79-6dd1feb61879@googlegroups.com \
--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