2.1 migration and smartcard stub

NIIBE Yutaka gniibe at fsij.org
Mon Nov 2 06:55:53 CET 2015


I pushed my change for this with message changed and adding comments

On 10/17/2015 12:02 AM, NIIBE Yutaka wrote:
> Hello,
> At Debconf15, I was asked about 2.1 migration.  The bug is filed
> in Debian:
>     gnupg2: gnupg 2.1 secret keys migration skips keys on smartcard
>     https://bugs.debian.org/795881
> I think that GnuPG 2.1 should emit some message for smartkey stub.
> In the end of this message, I put my proposal patch.  It memorizes if
> there were stub in private key migration, and if so, emit a message
> which suggests invocation of "gpg --card-status" with smartcard.
> Currently, the message is:
>     To migrate private key stubs for smartcard, run: gpg --card-status with smartcard
> But, I'm not sure if new PO message is worth for that.  I'm not sure
> if "gpg" in the message would be better than "gpg2" (there are
> instances of "gpg" as well as "gpg2" in existing code to emit
> messages), or not.
> I'm not good at using plural form.  Please correct the message string.
> Situation is: Private key (or private sub key) for smartcard has a
> stub (reference) to the specific card, instead of key material (which
> is on the card).  A single smartcard can have multiple private
> (sub)keys.  A user can use multiple smartcards.  If a user uses
> multiple smartcards, invocation should be done for each smartcard.
> Perhaps, it would be good not to expose internal term "stub", and
> following would be better:
>     To migrate secring.gpg for smartcard, with each smartcard, run:
>        gpg --card-status

More information about the Gnupg-devel mailing list