From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 601867943936 X-Google-Groups: supmua X-Google-Thread: 3030fda1bf,f9f4b5968d79362e X-Google-Attributes: gid3030fda1bf,domainid0,public,googlegroup X-Google-NewGroupId: yes X-Received: by 10.180.109.34 with SMTP id hp2mr8855680wib.4.1426599071104; Tue, 17 Mar 2015 06:31:11 -0700 (PDT) X-BeenThere: supmua@googlegroups.com Received: by 10.152.225.132 with SMTP id rk4ls39812lac.50.gmail; Tue, 17 Mar 2015 06:31:10 -0700 (PDT) X-Received: by 10.112.98.38 with SMTP id ef6mr9231231lbb.3.1426599070669; Tue, 17 Mar 2015 06:31:10 -0700 (PDT) Return-Path: Received: from li473-64.members.linode.com (nol.smallsoft.com. [176.58.108.64]) by gmr-mx.google.com with ESMTP id i8si130977wif.1.2015.03.17.06.31.10 for ; Tue, 17 Mar 2015 06:31:10 -0700 (PDT) Received-SPF: none (google.com: mail@johslarsen.net does not designate permitted sender hosts) client-ip=176.58.108.64; Authentication-Results: gmr-mx.google.com; spf=none (google.com: mail@johslarsen.net does not designate permitted sender hosts) smtp.mail=mail@johslarsen.net Received: from localhost (unknown [90.149.27.122]) by li473-64.members.linode.com (Postfix) with ESMTPSA id E9E6B2E18E81; Tue, 17 Mar 2015 13:31:09 +0000 (UTC) From: Johannes Larsen To: supmua Subject: Re: [sup] gpg-agent issue In-reply-to: <1426596032-sup-4861@frex230> References: <1426596032-sup-4861@frex230> Date: Tue, 17 Mar 2015 14:31:08 +0100 Message-Id: <1426598955-sup-8868@repos> User-Agent: Sup/git Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; boundary="=-1426599068-793592-29453-8949-1-=" --=-1426599068-793592-29453-8949-1-= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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 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=3D$(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 --=-1426599068-793592-29453-8949-1-= Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJVCCycAAoJENO88Xmyb6smLi0P/19klUzccZYd35t2FZftU5Me +viAKiLTI1jL1ZccMf8KTX+FJI4vVN9htNjd0zixlDhiQlfr5kcYsJrWv9KyRp0E gEeK97I1qkl5InWWVvo7d0+mNkfzk3MqIjD/P4PyNI7CLSU3sKcmXnlncb37N2RO RidcWpLu2ioXakbb5y+U8NjajDdaBnxAvJIY1hA9/hI47kPc0IAZGLQ6v9NC/BL0 FIGS69xGvnTXc4ex/iNU58fg1kL2wLh2VETQJZt5hgELLvnp4NvTAqXTaPBNtqWx ziWcExPmPzDs9U61PiF5UJBLcjc1PojARy6XHo3Fg/sKSs9sQzbKo/kHBEdoyLZ0 GsBdmbE4bBC6lTpSvTbpPL+mXgUJTrTCpXCYZ6K8wl0CzL7sFLm3udqib4Y8vedw cR7LBZgnbIj6rfmkFmMF6IYg6vtusB98ZwFdym5bQUAb5B2yPJOpiqYbdmDpSZvA RF9jxPVt41LSmDgLsu1bVqR9oDdCumWFG5rJ2hjomfOEG74r0Dr9nRnH33zLluCS x+rYxAXA7YIgRMn4ynbQndfWse5fLxRF932piriehMEsfzA1ZwUhCoMtpYHlBki+ fXWsrJ4M0NZzYcqyVtS433jDbyHTHE53NlIhYBQc3oikiPAvtfHG+e7QPIskNZkF jg0U1/ACvQ/LDOHtpgdi =/2JQ -----END PGP SIGNATURE----- --=-1426599068-793592-29453-8949-1-=--