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!
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
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
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
Hello,
I am trying to set up agent forwarding as per
https://wiki.gnupg.org/AgentForwarding. Everything is generally working,
but the remote gpg is prompting for passphrases
despite gpg-preset-passphrase having been used against local agent.
Forwarding normal socket (instead of extra socket) make
I am trying to set up agent forwarding as per
https://wiki.gnupg.org/AgentForwarding. Everything is generally working,
but the remote gpg is prompting for passphrases
despite gpg-preset-passphrase having been used against local gpg agent.
Forwarding normal socket (instead of extra socket) makes th
