Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • (I don't know why it has the key ID twice.) > Could it be showing up twice because you signed it with your master key? Perhaps it would list the issuer key ID as your master key, and keyid as the subkey if you had signed it with one?
    – IQAndreas
    Commented Sep 20, 2014 at 7:44
  • Nice theory, but I just checked and it's not a master cert/signing subkey thing (that's what my keys are like), the twing key IDs are whichever key made the signature. It'll be something to do with the subpacket it refers to in the signature packet, but I forget which bit of the RFC is relevant and I'm a little too tired to unearth it now (sorry). I can see how you drew that conclusion though, it does make some kinda sense.
    – Ben
    Commented Jun 19, 2015 at 9:38
  • 1
    From what I've read about the OpenPGP packet format recently, it simply makes less sense than X.509. Which says a lot about how little sense it makes. Commented Jun 19, 2015 at 12:42
  • I'm trying to verify GnuPG used the hash I specified with --s2k-digest-algo SHA256 (also see here). begin of digest eb 31 is pretty much useless. How can we determine the hash used when a detached signature is available?
    – jww
    Commented Dec 28, 2018 at 2:37