Download

Windows
Version Operating System
0.91-beta Windows XP, Vista, 7, 8, 8.1 (Both 32- and 64-bit)
0.91-beta for Windows
0.91-beta signed hash file
Offline Signing Key (0x98832223)
Mac/OSX
Version Operating System
0.91-beta Mac/OSX 10.7, 10.8, 10.9, 10.9.1, 10.9.2 (64-bit)
0.91-beta for Mac/OSX
0.91-beta signed hash file
Offline Signing Key (0x98832223)
Ubuntu/Debian Packages
Version Operating System
0.91-beta Ubuntu 12.04+ (64-bit)
0.91-beta for Ubuntu
0.91-beta signed hash file
Offline Signing Key (0x98832223)
0.91-beta Ubuntu 12.04+ (32-bit)
0.91-beta for Ubuntu
0.91-beta signed hash file
Offline Signing Key (0x98832223)
0.90-beta for Ubuntu 10.04 through 11.10 (32- and 64-bit) Ubuntu 10.04 through 11.10 (32- and 64-bit)
0.90-beta for Ubuntu 10.04 through 11.10 (64-bit)
0.90-beta for Ubuntu 10.04 through 11.10 (32-bit)

These packages are signed with our offline GPG key (0×98832223)  using dpkg-sig.

In addition to the first-time Bitcoin-Qt/bitcoind synchronization step, Armory will also build its own set of databases the first time. This will take between 30 min and 3 hours depending on your system. It is recommended you do not interrupt this step. After it completes, subsequent loads of Armory will usually be under 30 seconds.

Offline Bundles
Version Operating System
0.91-beta Raspberry Pi Raspbian (armhf) (32-bit)
0.91-beta for Raspberry Pi
0.91-beta signed hash file
Offline Signing Key (0x98832223)
0.90-beta Ubuntu/Debian 12.04
0.90-beta for Ubuntu/Debian 12.04 (64-bit)
0.90-beta for Ubuntu/Debian 12.04 (32-bit)
0.90-beta signed hash file
Offline Signing Key (0x98832223)
0.90-beta Ubuntu/Debian 10.04
0.90-beta for Ubuntu/Debian 10.04 (64-bit)
0.90-beta for Ubuntu/Debian 10.04 (32-bit)

Signed hashes

Offline signing key (Fingerprint: 0×98832223).

Verifying Downloaded Files

Armory is used by some of the most heavily-invested, and most paranoid Bitcoin enthusiasts for maximum privacy and security.  If you are in this category, it is recommended you verify that your Armory installers have not been altered in any way.  Armory Ubuntu/Debian packages (*.deb files) are signed directly using our Offline Signing Key (GPG) (0×98832223).  And each release comes with a signed file containing the SHA256 hashes of each installer.   Unfortunately, it is not easy to verify these signatures unless you have access to a Linux machine.  At the moment, the verification procedure on Windows is very difficult.

To verify in Linux, “cd” to the directory containing the installer (usually Downloads), download and import the Armory signing key from the ubuntu key-server, install the signature verification program, and then use it verify the signatures on the *.deb files:

$ cd Downloads   # the directory containing the *.deb
$ gpg --recv-keys --keyserver keyserver.ubuntu.com 98832223
$ sudo apt-get install dpkg-sig
$ dpkg-sig --verify *.deb

If everything goes smoothly, you will see the following output:

$ 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 (Offline Signing Key) <alan@bitcoinarmory.com>"
$ dpkg-sig --verify *.deb
Processing armory_0.85-beta_amd64.deb... 
GOODSIG _gpgbuilder 821F122936BDD565366AC36A4AB16AEA98832223 1353699840

Notice the “98832223″ at the end of the “GOODSIG” line. That is the key “Fingerprint” and if it does not match, do not use that installer! To be extra sure, you can check the last 16 characters, which should be “4AB16AEA 98832223″.