
<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><span></span></div><div><meta http-equiv="content-type" content="text/html; charset=utf-8"><div><span></span></div><div><span>Hello all,</span></div><div><span></span><br><blockquote type="cite"><span>On 14 Aug 2018, at 13:43, Damien Goutte-Gattat via Gnupg-users <<a href="mailto:gnupg-users@gnupg.org">gnupg-users@gnupg.org</a>> wrote:</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><blockquote type="cite"><span>On 08/14/2018 12:05 PM, Ralph Corderoy wrote:</span><br></blockquote></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><blockquote type="cite"><span>A [V4] fingerprint is the 160-bit SHA-1 hash of the octet 0x99,</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>followed by the two-octet packet length, followed by the entire</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>*Public-Key packet* starting with the version field.</span><br></blockquote></blockquote><span></span><br><span></span>Following on from this, in my experience, studying the output of the `—list-packets` option has been one of the most effective ways of learning how GnuPG works.</div><div><br></div><div>See <a href="https://gnupg.org/documentation/manuals/gnupg/Operational-GPG-Commands.html#index-list_002dpackets">https://gnupg.org/documentation/manuals/gnupg/Operational-GPG-Commands.html#index-list_002dpackets</a> .</div><div><br></div><div>Andrew</div></div></body></html>