On 28/02/18 20:59, Werner Koch wrote:
> But that is about gpg and not about gpgsm.
Currently, it's not that easy to get the keygrip for an OpenPGP
smartcard key.
For keys for which the public part is available, it's:
$ gpg --card-status
Note desired KEYID
$ gpg --with-keygrip -k $KEYID
Find the K
On Wed, 28 Feb 2018 16:30, thomas.jaro...@intra2net.com said:
> what do you think about Peter's idea:
>
> $ gpg --with-keygrip --card-status
If you use that with --with-colons you can also script this.
But that is about gpg and not about gpgsm. gpgsm has no external card
interface because the e
On Wednesday, 28 February 2018 14:50:39 CET Werner Koch wrote:
> If you need this information a small tool to present an enhanced menu
> could be written. That tool would then utilize gpgsm and gpg. GPA
> might be a candidate to implement this.
what do you think about Peter's idea:
$ gpg --with
On Wed, 28 Feb 2018 10:56, thomas.jaro...@intra2net.com said:
> When using a smartcard, what about showing the openpgp key IDs
> in the "Available keys" menu?
gpgsm does and shall not know anything about OpenPGP. Thus it can't
display OpenPGP information. In theory we could display the fingerpr
On 28/02/18 10:56, Thomas Jarosch wrote:
> When using a smartcard, what about showing the openpgp key IDs
> in the "Available keys" menu?
I don't think that's possible: keygrips are "protocol" agnostic, but key
IDs are not. So while the keygrip is the same for S/MIME and OpenPGP,
key ID's are inhe
Hi.
Am Mittwoch, den 28.02.2018, 10:56 +0100 schrieb Thomas Jarosch:
> To me it seems it shows the 'keygrip' instead of the smartcard key
> IDs?
Yes, that's correct.
> When using a smartcard, what about showing the openpgp key IDs
> in the "Available keys" menu?
I think this is not neccessary,
Hello together,
gpgsm can be used to create X.509 certificates
for existing secret keys on a openpgp smartcard.
"gpg2 --card-status" looks like this:
*
..
Signature key : E642 8DAC 275A 3247 5B59 A16F A3E9 1268 663A 9918
created : 2018-0
