Bitcoin Armory Difference in GPG Output The section "Verifying Downloaded Files' at http://bitcoinarmory.com/download/ says that I should see the following output after running GPG:

$ gpg --recv-keys --keyserver keyserver.ubuntu.com 98832223
gpg: requesting key 98832223 from hkp server keyserver.ubuntu.com
gpg: key 98832223: public key "Alan C. Reiner (Armory Signing Key) &lt;alan.reiner@gmail.com&gt;"


However when I ran it, I got:

gpg: key 98832223: public key "Alan C. Reiner (Offline Signing Key) &lt;alan@bitcoinarmory.com&gt;" imported 


instead. A link I found on btcarmory.org (http://pgp.mit.edu:11371/pks/lookup?search=Armory+Signing) has a result that implies that these two outputs are acceptable, but can someone please confirm that this is true?

Is the difference in the GPG output a concern? I only ask because of how intensely it is suggested to do this stuff! Thanks.
The output is fine. The key fingerprint is the same. Alan merely has several uid records in this key.

See for yourself:

$ gpg --list-key 98832223
pub   4096R/98832223 2012-02-28
uid                  Alan C. Reiner (Offline Signing Key) &lt;alan@bitcoinarmory.com&gt;
uid                  Alan C. Reiner (Armory Signing Key) &lt;etotheipi@gmail.com&gt;
uid                  Alan C. Reiner (Armory Signing Key) &lt;alan.reiner@gmail.com&gt;
sub   4096R/DE6B2D74 2012-02-28


GnuPG simply chose to show you one of the other, completely valid uids for this key.