On Fri, Jul 3, 2015 at 7:08 AM, Arjan Wekking <[email protected]> wrote: > Now, if you were only to generete these message-id’s for private key pairs, I > assume it would probably never be an issue. But if you were to add public > keys as well, then using fingerprints instead of (long) key ID’s would > perhaps be better. >
SKS keyservers accept lookups for both short and long key ids, fingerprints, and word searches on user ids[1]. Perhaps the Message-ID should be the fingerprint + user ids (i.e. "0xf75be... Daniel Roesler <[email protected]>"), so that a client can easily index/search their mailbox for the keys they want to use (I might have multiple private keys for work and personal). It might be a bit of an issue with UTF-8 user ids, though. Can a Message-ID be UTF-8? Also, it looks like OpenPGP.js doesn't support gpg --export-secret-subkeys files yet[2]. Daniel [1]: https://bitbucket.org/skskeyserver/sks-keyserver/src/1a1b0b48e642449527e2ddafb761352f339a2636/dbserver.ml?at=default#cl-202 [2]: https://github.com/openpgpjs/openpgpjs/issues/251 _______________________________________________ Gnupg-users mailing list [email protected] http://lists.gnupg.org/mailman/listinfo/gnupg-users
