[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: How to transition to a new UID?



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 14.02.2012 13:48, Wolodja Wentland wrote:
> Following the discussion in [2] and most importantly [3] it seems
> as if the primary UID is not really important as any UID is
> acceptable if the real name matches.

I can confirm that. That's how I can upload, as keyring maintainers
ignored my desired UID when importing my key into the DM keyring so I
rely on the name for matching an upload with a key ID. That said, this
seems a fragile setting to me, generally speaking.

> As this holds true for my key it seems to me as if the best course
> of action right now would be to keep on using my old UID until the
>  update has been incorporated into the maintainer keyring. Once
> that happens I can start to use the new one and can upload without 
> problems.

Should be so. Either that, or you become DD where rules are more
flexible. ;-)

> Are there other aspects of a UID change that I am overlooking?

As long as either your name or your UID matches, you are fine. That
said, I am not sure how exactly the key transition works for DMs. I
could be wrong, but I think there is no automated update or a DM's
keyring.

- -- 
with kind regards,
Arno Töll
IRC: daemonkeeper on Freenode/OFTC
GnuPG Key-ID: 0x9D80F36D
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJPOqQrAAoJEMcrUe6dgPNt5/IQAKaW+imkOUzTVXuwOmHOAfNu
rEM4I6ZP3HRdmsBSxPWtLvy3pUA4rJnBkMJfa9KuVl9CNpdRq09T1hgixGUIKXCK
SXrarxTlPeEYBz2f3/iH1YW2tUKTx9krJjWT1DUy/OA7sQx2ybh4Eh9abJT7TPJq
zTkxQ2LQquRrosh6NG1Jdx1A9kRSlu1pYMfPic7ltT8hg+ajXS6Npqqz1axRjwRH
M6aevwKMwBHAS7mvvrWMsTYYkYrQ4X7MJoInsQt5nZkYiE44AXvE7l5olUbFzTu5
jIirmX46npUNdDVmFRdHlZxdeIH+QTeci0FLImu7ZZHAohBeUzdr+0ozRO8w6n/V
CSAyq7qpCn9oHkhgwT+U8gRU+amaIsI9tSIvBDlZITINqJf8gbkMqMrQCxxFlTej
8sRzMX8c6jpHsPXnqDPz2xmG6QvdHQ2YKutuAVEXbelMD7ZMzZXYtSrIzO5K+AmW
MdYvW15+4e4LtoI74djhutS3zXPkIFpdW3FMvxiriDTq+przuf+XjHEwYStewUqy
aZDelDkx8ye1bNK07NpPOXlNln8S7UQderzGBKtNdBXP8+UIhNH8SEXe/JG/Yyol
iX8gZgZed5dJ8/9BSiwn6MlAYdKSoPUpoJvQxTf4W/OMsf5YFcNqy5fzKor8Ac78
ov7253vzwKVPO9u0QmN3
=vdEe
-----END PGP SIGNATURE-----


Reply to: