Armory Ubuntu/Debian 0.96.0 signed with a different key than listed on the website I downloaded the Armory version for Ubuntu/Debian from here:
https://www.bitcoinarmory.com/download/

Under the "Offline Signing Key" section it lists the public key for verification to be: 98832223.   This key is also used throughout their verification instructions.  They also show the fingerprint for this key on that page.

However, the files I downloaded are signed with key 4922589A.  I looked that key up on pgp.mit.edu and it shows the key owned by "goatpig (Offline signing key for Armory releases)"  Now, I see that goatpig is the name of one of the contributors on github, but really anyone can make a key with that name and since the website doesn't reference the key, or give me a fingerprint for the key, that I can find, I am hesitant to trust it.

My question here really is, can anyone confirm what the proper public key is to verify the armory downloads.  Did I miss something?

--update

I see there are two armory websites  www.bitcoinarmory.com and btcarmory.com.  each has a 0.96.0 download and the hash of both installs are the same, so I assume they are the same file, they are also both signed with the same public key.  The difference is that bitcoinarmory.com says to verify with 98832223 and btcarmory says to verify with 4922589A.  Very confusing, but my best guess is that  4922589A is actually the proper key to verify the signature with.  Either way, I think I'm just going to stick with bitcoin-qt unless someone can help clear this up.
https://bitcoinarmory.com is no longer Armory's official website. The official website is actually https://btcarmory.com. bitcoinarmory.com still hosts the new binaries, but they are only a mirror and everything else on the site is outdated.

Since Armory's development changed a few years ago, the actual release signing key is 4922589A as that is the new maintainer's signing key. This key is used on Armory 0.94.0 and above. The old signing key, 98832223, is the old maintainer's signing key.