Resolving multiple primary user IDs and self-signatures

[David Shaw <[e-mail]>]

Here are two suggestions to help with resolving multiple user IDs
marked primary, as well as resolving multiple self-signatures with
different subpackets:

From 5.2.3.19. Primary user id:

   This is a flag in a user id's self signature that states whether
   this user id is the main user id for this key. It is reasonable for
   an implementation to resolve ambiguities in preferences, etc. by
   referring to the primary user id. If this flag is absent, its value
   is zero. If more than one user id in a key is marked as primary, the
   implementation may resolve the ambiguity in any way it sees fit,
|  but it is RECOMMENDED that priority be given to the user ID with
|  the most recent self signature.

From 5.2.3.3. Notes on Self-Signatures:

   Since a self-signatures contain important information about the
   key's use, an implementation SHOULD allow the user to rewrite the
   self-signature, and important information in it, such as preferences
   and key expiration.
|  An implementation that encounters multiple self-signatures on the
|  same object may resolve the ambiguity in any way it sees fit, but
|  it is RECOMMENDED that priority be given to the most recent
|  self-signature.

David

-- 
   David Shaw  |  [e-mail]  |  WWW http://www.jabberwocky.com/
+---------------------------------------------------------------------------+
   "There are two major products that come out of Berkeley: LSD and UNIX.
      We don't believe this to be a coincidence." - Jeremy S. Anderson