2

Whenever I generate a new 4096 RSA key in my GPG program and export the public key to a text file, I get a text file containing a total of around 52 lines (it varies, one of them is 53 lines).

However, I just imported a public key from another guy I found on his website. My GPG program shows that his key length is also 4096. However, his key was only 30 lines, not even close to 52-53.

What explains this difference? How can he have such a short public key even for 4096?

The line width is 64 characters in every case (where the key is at full width, which is most of lines).

When I counted the liens, I started at "-----BEGIN PGP PUBLIC KEY BLOCK-----" and ended at "-----END PGP PUBLIC KEY BLOCK-----".


Updates:

I found the reason. My key contains both "sig" and "sig 3" with the same ID. The other guy's key contains only the "sig". This explains the difference, I guess.

My questions now:

Why should I keep the "sig 3"? Why where both "sig" and "sig 3" generated for me?

When I export the public key, my program doesn't give me any option to pick only one of them. It's either all or nothing.

Is there any good reasons to provide people with both "sig" and "sig 3"?

What do you recommend I do?

  • 1
    I suspect his key is encoded in a different format than yours (not sure if this is possible - I'm by all means no RSA specialist). If it is decoded to binary representation, both keys (yours and his) should be exactly 4096 bits. – Steven Volckaert Apr 26 '14 at 11:26
  • @Steven I found the reason. Will update question soon. – cryptonamus Apr 26 '14 at 11:40
  • Useful reading: we.riseup.net/riseuplabs+paow/openpgp-best-practices? – Deer Hunter Apr 26 '14 at 11:56

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.