Re: gpg-preset-passphrase: caching passphrase failed: Forbidden

2024-12-11 Thread Werner Koch via Gnupg-users
On Tue, 10 Dec 2024 17:04, Elliott de Launay said: > Reloading the agent via `gpg-connect-agent reloadagent /bye`, results in BTW, "gpgconf --reload gpg-agent" is a frontend for this. >> gpg-connect-agent: connection to agent is in restricted mode >> ERR 67109115 Forbidden You are using a remo

Re: gpg-preset-passphrase and extra agent socket

2023-03-27 Thread xeyrion--- via Gnupg-users
On Mon, Mar 27, 2023 at 5:58 AM Werner Koch wrote: > You are right. I forgot about this. > > You need to wait for the next version or apply the attached patch and > run gpg-preset-passphrase with the option --restricted to address the > other cache. > Great, thanks for confirming and the patch!

Re: gpg-preset-passphrase and extra agent socket

2023-03-27 Thread Werner Koch via Gnupg-users
On Sat, 25 Mar 2023 18:56, xeyrion--- said: > The difference seems to be that normal socket uses ".0" as cache key while > extra socket uses ".1" and therefore misses? You are right. I forgot about this. You need to wait for the next version or apply the attached patch and run gpg-preset-passph

Re: gpg-preset-passphrase and extra agent socket

2023-03-25 Thread xeyrion--- via Gnupg-users
On Fri, Mar 24, 2023 at 5:20 AM Werner Koch wrote: > On Wed, 22 Mar 2023 16:16, xeyrion--- said: > > > Forwarding normal socket (instead of extra socket) makes the prompt go > > away. Is there a way to preset passphrase for extra socket as well? > > The caching behavior does not depend on the con

Re: gpg-preset-passphrase and extra agent socket

2023-03-24 Thread Werner Koch via Gnupg-users
On Wed, 22 Mar 2023 16:16, xeyrion--- said: > Forwarding normal socket (instead of extra socket) makes the prompt go > away. Is there a way to preset passphrase for extra socket as well? The caching behavior does not depend on the connection type. Thus this should not be an issue. I assume you

Re: gpg-preset-passphrase installation and usage

2019-04-15 Thread gnupg
Walia, Gaurav (333G) via Gnupg-users wrote: > Ok. Did some googling came up with the following. Could someone confirm > that I’m doing this correctly? > > Objective: To save passphrase in cache to an unattended machine so that it > doesn’t time out the credentials. Specifically, using > htt

Re: gpg-preset-passphrase installation and usage

2019-04-13 Thread Peter Lebbing
On 13/04/2019 14:34, Peter Lebbing wrote: > Either reload the agent (this will make it forget all passphrases) Of course I should have made that explicit. You reload the agent by: $ gpgconf --reload gpg-agent I should mention this before you start figuring out a way to send it SIGHUP (which btw

Re: gpg-preset-passphrase installation and usage

2019-04-13 Thread Peter Lebbing
Hello! On 13/04/2019 12:42, Walia, Gaurav (333G) via Gnupg-users wrote: > * gpg --version > o gpg (GnuPG) 2.0.22 This version is a full six years old. Not only is 2.0.22 unsupported, the whole 2.0 branch has been end-of-life for a good bit more than a year now. How come you're using some

Re: gpg-preset-passphrase installation and usage

2019-04-13 Thread Walia, Gaurav (333G) via Gnupg-users
Ok. Did some googling came up with the following. Could someone confirm that I’m doing this correctly? Objective: To save passphrase in cache to an unattended machine so that it doesn’t time out the credentials. Specifically, using https://github.com/docker/docker-credential-helpers, with se

Re: gpg-preset-passphrase not working with 2.1

2016-07-18 Thread Justus Winter
Hello :) David Matthews writes: > I can't get gpg-preset-passphrase to work with GnuPG 2.1.7. The > command appears to work successfully but the passphase is not found by > GET_PASSPHRASE. I've included details of my simple test below plus the > output from running it on Centos 7.2 (where it wor

Re: gpg-preset-passphrase not working with 2.1

2016-07-18 Thread David Matthews
On 14 July 2016 at 07:29, David Matthews wrote: > On 13 July 2016 at 13:13, Daniel Kahn Gillmor wrote: >> Hi David-- >> >> On Tue 2016-07-12 16:46:53 +0200, David Matthews wrote: >>> I can't get gpg-preset-passphrase to work with GnuPG 2.1.7. >> >> there have been significant changes to GnuPG bet

Re: gpg-preset-passphrase not working with 2.1

2016-07-13 Thread David Matthews
On 13 July 2016 at 13:13, Daniel Kahn Gillmor wrote: > Hi David-- > > On Tue 2016-07-12 16:46:53 +0200, David Matthews wrote: >> I can't get gpg-preset-passphrase to work with GnuPG 2.1.7. > > there have been significant changes to GnuPG between 2.1.7 and 2.1.13. > > can you try upgrading to 2.1.1

Re: gpg-preset-passphrase not working with 2.1

2016-07-13 Thread Daniel Kahn Gillmor
Hi David-- On Tue 2016-07-12 16:46:53 +0200, David Matthews wrote: > I can't get gpg-preset-passphrase to work with GnuPG 2.1.7. there have been significant changes to GnuPG between 2.1.7 and 2.1.13. can you try upgrading to 2.1.13? --dkg ___ Gnu

Re: gpg-preset-passphrase: cache id

2013-05-27 Thread Werner Koch
On Mon, 27 May 2013 14:02, mailinglis...@hauke-laging.de said: > How is a passphrase with a cache id like foo:12346 used? Is it tried for all > keys which do not have a keygrip entry? No. It is used with the commands GET_PASSPHRASE [--data] [--check] [--no-ask] [--repeat[=N]]

Re: gpg-preset-passphrase

2010-03-08 Thread kkaputa
I have a patch for fixing the 'forget' option. I hope this is of some help. http://old.nabble.com/file/p27817136/clear_passphrase.patch clear_passphrase.patch It would be nice to have a more complete tool for administering passphrases, or a simpler interface to pinentry :) /K Daniel Eggle