diff options
| author | NIIBE Yutaka <gniibe@fsij.org> | 2017-01-18 07:48:50 +0100 |
|---|---|---|
| committer | NIIBE Yutaka <gniibe@fsij.org> | 2017-01-18 08:03:47 +0100 |
| commit | 79cea89774e6327b6785e22b7057f9e3e188ac2b (patch) | |
| tree | 6ac0f0a6e4df8a0d4995617c5a0fc9f659cbd3f4 /doc/scdaemon.texi | |
| parent | scd: Add "card_list" sub command for GETINFO. (diff) | |
| download | gnupg2-79cea89774e6327b6785e22b7057f9e3e188ac2b.tar.xz gnupg2-79cea89774e6327b6785e22b7057f9e3e188ac2b.zip | |
scd: Cleanup SERIALNO protocol.
* scd/app.c (app_get_serial_and_stamp): Remove.
(app_get_serialno): New.
(app_write_learn_status): Use send_status_direct.
(app_getattr): Use app_get_serialno for SERIALNO and
send with send_status_direct.
* scd/app-openpgp.c (do_getattr): Likewise.
* scd/command.c (cmd_serialno): Don't send TIMESTAMP of 0.
(cmd_learn): Likewise. Don't inquire with TIMESTAMP of 0.
--
In the SERIALNO protocol, timestamp used to be considered, but had never
used at all. In the new implementation, removed card/token is always
detected and connection becomes invalid, no timestamp is required any
more. Examined scute and poldi as well for this protocol change.
Signed-off-by: NIIBE Yutaka <gniibe@fsij.org>
Diffstat (limited to 'doc/scdaemon.texi')
| -rw-r--r-- | doc/scdaemon.texi | 7 |
1 files changed, 3 insertions, 4 deletions
diff --git a/doc/scdaemon.texi b/doc/scdaemon.texi index 4cf44bccb..161780178 100644 --- a/doc/scdaemon.texi +++ b/doc/scdaemon.texi @@ -516,11 +516,10 @@ done on the same card unless he call this function. Return the serial number of the card using a status response like: @example - S SERIALNO D27600000000000000000000 0 + S SERIALNO D27600000000000000000000 @end example -The trailing 0 should be ignored for now, it is reserved for a future -extension. The serial number is the hex encoded value identified by +The serial number is the hex encoded value identified by the @code{0x5A} tag in the GDO file (FIX=0x2F02). @@ -537,7 +536,7 @@ used without the @option{--force} option, the command might do an INQUIRE like this: @example - INQUIRE KNOWNCARDP <hexstring_with_serialNumber> <timestamp> + INQUIRE KNOWNCARDP <hexstring_with_serialNumber> @end example The client should just send an @code{END} if the processing should go on |