On Wed, 10 Apr 2024 12:15, Todd Zullinger said:
> This caused me to re-read the document and I'll likely add
> an additional Token: line to note the two cards which hold a
> new key (which I have yet to start using). That should make
That is actually there (TOKEN, see the example) and gpg-agent
Hi,
Werner Koch via Gnupg-users wrote:
> On Fri, 5 Apr 2024 13:03, Todd Zullinger said:
>
>> In such a case, it sounds like it may be reasonable to use
>> the normal socket? Until the remote side is updated to
>
> In fact, I also did this for some time but later came up with
>
> CommitDate
On Fri, 5 Apr 2024 13:03, Todd Zullinger said:
> In such a case, it sounds like it may be reasonable to use
> the normal socket? Until the remote side is updated to
In fact, I also did this for some time but later came up with
CommitDate: Wed Oct 12 11:30:35 2022 +0200
agent: Introduce
Bee via Gnupg-users wrote:
> In the mean time, you could put something along the lines of:
>
> {CmdCalls ; } 2>&1 | grep -v -e "^gpg: problem with fast path key
> listing: Forbidden - ignored$" or something, to keep that output out
> of your stderr stream.
I think there's a downside to that (but
Hi Werner,
Werner Koch via Gnupg-users wrote:
>> gpg: problem with fast path key listing: Forbidden - ignored
>
> I'll suppress that message in --quiet mode for the next release.
Excellent, thanks!
> When doing a secret key listing (which happens with -K but also in
> --with-colons mode) gp
In the mean time, you could put something along the lines of:
{CmdCalls ; } 2>&1 | grep -v -e "^gpg: problem with fast path key
listing: Forbidden - ignored$" or something, to keep that output out
of your stderr stream.
If something else unexpected displays, you'll get more issues, but
then you p
Hi!
> gpg: problem with fast path key listing: Forbidden - ignored
I'll suppress that message in --quiet mode for the next release.
When doing a secret key listing (which happens with -K but also in
--with-colons mode) gpg walks over all public keys and asks the agent
for each key whether a
Hi,
I have been working on setting up agent forwarding¹.
One issue which I have not yet found a solution for is that
gpg prints the following to stderr when performing actions
involving the agent:
gpg: problem with fast path key listing: Forbidden - ignored
Both hosts are running gnupg-2.4.
