mirror of
git://git.gnupg.org/gnupg.git
synced 2024-06-07 23:27:48 +02:00
agent: Silence error messages for READKEY --card
* agent/command.c (cmd_readkey): Test for shadow key before creating
it.
(cherry picked from commit 8f2c9cb735
)
This commit is contained in:
parent
2af217ecd7
commit
aa612d752e
|
@ -1030,9 +1030,13 @@ cmd_readkey (assuan_context_t ctx, char *line)
|
|||
goto leave;
|
||||
}
|
||||
|
||||
if (agent_key_available (grip))
|
||||
{
|
||||
/* (Shadow)-key is not available in our key storage. */
|
||||
rc = agent_write_shadow_key (grip, serialno, keyid, pkbuf, 0);
|
||||
if (rc)
|
||||
goto leave;
|
||||
}
|
||||
|
||||
rc = assuan_send_data (ctx, pkbuf, pkbuflen);
|
||||
}
|
||||
|
|
|
@ -44,9 +44,8 @@ convention. Example (here indented with two spaces):
|
|||
(#D2760001240102000005000011730000# OPENPGP.1)
|
||||
)))
|
||||
|
||||
GnuPG 2.2 is able to read and update keys using the new format, but
|
||||
will not create new files using the new format. Furthermore, it only
|
||||
makes use of the value stored under the name 'Key:'.
|
||||
GnuPG 2.2 is also able to read and write keys using the new format
|
||||
However, it only makes use of the value stored under the name 'Key:'.
|
||||
|
||||
Keys in the extended format can be recognized by looking at the first
|
||||
byte of the file. If it starts with a '(' it is a naked S-expression,
|
||||
|
|
Loading…
Reference in New Issue
Block a user