From: Johannes Larsen <mail@johslarsen.net>
To: supmua <supmua@googlegroups.com>
Subject: Re: [sup] gpg-agent issue
Date: Tue, 17 Mar 2015 14:31:08 +0100 [thread overview]
Message-ID: <1426598955-sup-8868@repos> (raw)
In-Reply-To: <1426596032-sup-4861@frex230>
[-- Attachment #1: Type: text/plain, Size: 993 bytes --]
gpg-agent caches the passphrase for a limited time (a couple of hours if
remember correctly). to check if this is the problem try signing a file
(thereby providing gpg-agent with a passphrase) then start sup in the
same shell and check if its signs emails. the time gpg-agent caches the
passphrase can be changed with: (~/.gnupg/gpg-agent.conf)
max-cache-ttl <SECONDS>
if the passphrase caching is not the problem you might have initiated
gpg-agent insufficiently. this is what I source from ~/.bashrc to
initiate the gpg-agent or connect to a running gpg-agent:
if [ -f "${HOME}/.gpg-agent-info" ]; then
. "${HOME}/.gpg-agent-info"
export GPG_AGENT_INFO
fi
gpg-agent --daemon --write-env-file "${HOME}/.gpg-agent-info" --quiet &> /dev/null
export GPG_TTY=$(tty)
if you read `man gpg-agent` it mentions that exporting GPG_TTY is
important, so if you do not do this already, it might be a good place to
start.
--
johs (Johannes Larsen), (+47) 41435451
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-03-17 13:31 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
2015-03-17 13:31 ` Johannes Larsen [this message]
2015-03-17 13:33 ` [sup] " 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=1426598955-sup-8868@repos \
--to=mail@johslarsen.net \
--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