Hi there,
The opnPGP smartcards seem to have private data objects to store
arbitrary data, right? It seems even the old 1.1 version cards feature
these objects.
How do you write to these objects? Can GnuPG do this? I didn´t found any
way with --card-edit or --card-status. And can GnuPG read these
Hi,
On Thu, Jan 30, 2020 at 11:24:54PM +0100, mailing list via Gnupg-users wrote:
How do you write to these objects? Can GnuPG do this? I didn´t found
any way with --card-edit or --card-status.
You can use the (undocumented) command "privatedo" from GnuPG's
--card-edit menu. For example, to w
On 31.01.20 at 00:14 it was said by Damien Goutte-Gattat:
> On Thu, Jan 30, 2020 at 11:24:54PM +0100, mailing list via Gnupg-users
> wrote:
>> How do you write to these objects? Can GnuPG do this? I didn´t found
>> any way with --card-edit or --card-status.
>
> You can use the (undocumented) comm
> (...)
> You can use the (undocumented) command "privatedo" from GnuPG's
> --card-edit menu. For example, to write into the private DO #1:
> (...)
>> And can GnuPG read these objects?
>
> Yes. If a private DO contains a value, it will be listed in the output
> from the --card-status command.
I
On Fri, Jan 31, 2020 at 12:39:11AM +0100, mailing list wrote:
By the way, is mcl3 the length of the key currently living on the
smartcard or the maximum key length supported by this card?
Neither of those. It's the maximum length of the "Cardholder certificate
DO". This is another data object
On Fri, Jan 31, 2020 at 12:55:05AM +0100, mailing list wrote:
I hoped these objects may have been (read) protected by the PIN, but
they´re world readable if you have the card, a bit sad...
Only Private DOs #1 and #2 are readable without any PIN. Reading the
private DO #3 requires the user PIN,
