documentation icon indicating copy to clipboard operation
documentation copied to clipboard

Inconsistencies in Keysizes

Open berney opened this issue 9 years ago • 0 comments

First, this is a great guide, and I appreciate the effort you put into it.

In the Key Editor section the key CDCD72AF is clearly a 3072 bit RSA key, as described in the instruction when generating the key and selecting the keysize.

amnesia@amnesia:~$ gpg --edit-key CDCD72AF
Secret key is available.

pub  3072R/CDCD72AF  created: 2063-04-06  expires: 2063-04-06  usage: SC   
                     trust: unknown       validity: unknown
[ unknown] (1). Ada Lovelace <[email protected]>

However in the Smartcard Export section we see a 4096 bit RSA key: -

gpg> toggle

sec  4096R/CDCD72AF  created: 2063-04-06  expires: 2063-10-06
(1)  Ada Lovelace <[email protected]>

There are some other parts where CDCD72AF is 3072 bits and sometimes 4096 bits.

If they are to server as different examples perhaps they should have different IDs (e.g. scenarios where the Primary key with Certify capability is not on a smartcard, and cases where the Primary key is on a smartcard (hence the smaller 3072 bit size).

berney avatar Sep 13 '16 11:09 berney