5e7fcd079b
This way, clients can exert control over the state of the CardClient, e.g. to combine CardApp operations in a PCSC transaction. |
||
|---|---|---|
| .. | ||
| src | ||
| Cargo.toml | ||
| README.md | ||
scdaemon client for the openpgp-card library
This crate provides ScdClient, which is an implementation of the
CardClient trait that uses an instance of GnuPG's
scdaemon
to access OpenPGP cards.
Known limitations
-
Uploading RSA 4096 keys via scdaemon doesn't work with cards that don't support Command Chaining (e.g. the "Floss Shop OpenPGP Smart Card"). This is caused by a size limitation for client requests via the Assuan protocol. Assuan "Client requests" are limited to 1000 chars. Commands are sent as ASCII encoded hex, so APDU commands are limited to around 480 bytes. This is insufficient for importing RSA 4096 keys to the card (all other OpenPGP card operations fit into this constraint).
-
When using
scdaemonvia pcsc (by configuringscdaemonwithdisable-ccid), choosing a specific card of multiple plugged in OpenPGP cards seems to be broken. So you probably want to plug in one OpenPGP card at a time when usingopenpgp-card-scdccombined withdisable-ccid. -
When using
scdaemonvia its defaultcciddriver, choosing a specific one of multiple plugged in OpenPGP cards seems to only work up to 4 plugged in cards. So you probably want to plug in at most four OpenPGP cards at a time when usingopenpgp-card-scdcwith its ccid driver.