unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: David Shaw <dshaw@jabberwocky.com>
To: IETF OpenPGP Working Group <ietf-openpgp@imc.org>
Cc: notmuch <notmuch@notmuchmail.org>
Subject: Re: including the entire fingerprint of the issuer in an OpenPGP certification
Date: Mon, 17 Jan 2011 22:22:57 -0500	[thread overview]
Message-ID: <2885367E-D215-4BE7-983D-C82C55C64B0F@jabberwocky.com> (raw)
In-Reply-To: <4D34F133.3000807@fifthhorseman.net>

On Jan 17, 2011, at 8:47 PM, Daniel Kahn Gillmor wrote:

> Would there be any objection to a new subpacket type for OpenPGPv4 that
> would include the remaining 96 bits of the issuer's fingerprint?  (the
> "high 96" proposal)
> 
> Alternately, what about a new subpacket type that simply includes the
> entire 160 bits of the issuer's fingerprint?   (the "full fingerprint"
> proposal)

I like this idea.  I would do it as "full fingerprint" myself.  The difference in storage between 160 bits and 96 bits is all of 8 bytes.  I think the simplicity of being able to say the whole fingerprint is in there is worth a measly 8 bytes.

Do we necessarily need a new subpacket type for this?  It could pretty easily be a notation.

David

  parent reply	other threads:[~2011-01-18  3:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-18  1:47 including the entire fingerprint of the issuer in an OpenPGP certification Daniel Kahn Gillmor
2011-01-18  2:14 ` Jon Callas
2011-01-18  2:42   ` Peter Gutmann
2011-01-18  3:22 ` David Shaw [this message]
2011-01-18 10:01 ` Daniel A. Nagy
2011-01-19  0:11   ` Peter Gutmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://notmuchmail.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2885367E-D215-4BE7-983D-C82C55C64B0F@jabberwocky.com \
    --to=dshaw@jabberwocky.com \
    --cc=ietf-openpgp@imc.org \
    --cc=notmuch@notmuchmail.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://yhetil.org/notmuch.git/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).