NOTE

For latest news and release please see btcarmory.com

0.96.0 and Compatible with 0.14.0+ and Segwit

Thank you to all the contributors:

and the testers/bug reporters:

Downloads

0.96.0

0.95.1

0.93.3

![armory download][6] **Windows** * [Armory 0.93.3 for Windows XP, Vista, 7, 8+ (64-bit)](/downloads/bitcoinarmory-releases/armory_0.93.3_winAll.exe) ![armory download][3] **MacOSX** * [Armory 0.93.3 for MacOSX 10.7+ (64bit)](/downloads/bitcoinarmory-releases/armory_0.93.3_osx.tar.gz) ![armory download][5] **Ubuntu** * [Armory 0.93.3 for Ubuntu 12.04+ (32bit)](/downloads/bitcoinarmory-releases/armory_0.93.3_ubuntu-32bit.deb) * [Armory 0.93.3 for Ubuntu 12.04+ (64bit)](/downloads/bitcoinarmory-releases/armory_0.93.3_ubuntu-64bit.deb) ![armory download][4] **RaspberryPi** * [Armory 0.93.3 for RaspberryPi (armhf)](/downloads/bitcoinarmory-releases/armory_0.93.3_raspbian-armhf.tar.gz) * [Armory 0.93.3 Offline Bundle for Ubuntu 12.04 exact (32bit)](/downloads/bitcoinarmory-releases/armory_0.93.3_offline_ubuntu_12.04-32.tar.gz) * [Armory 0.93.3 Offline Bundle for Ubuntu 12.04 exact (64bit)](/downloads/bitcoinarmory-releases/armory_0.93.3_offline_ubuntu_12.04-64.tar.gz) * [Armory 0.93.3 Offline Bundle for RaspberryPi (armhf)](/downloads/bitcoinarmory-releases/armory_0.93.3_rpi_bundle.tar.gz) ![armory download][2] **Signed Hashes** * [Armory 0.93.3: Signed hashes of all installers](/downloads/bitcoinarmory-releases/armory_0.93.3_sha256sum.txt.asc) ![armory download][1] **Offline Signing Key** [Download Offline Signing Key](https://bitcoinarmory.com/Alan-C.-Reiner-Offline-Signing-Key-alan@bitcoinarmory.com-0x98832223-pub.asc) (0x98832223) Also available on [MIT PGP Public Key Server](http://pgp.mit.edu:11371/pks/lookup?search=bitcoinarmory+offline&op=index) You can also view the full [Changelog](https://bitcointalk.org/index.php?topic=963268.0). **NOTE: Offline bundles for Ubuntu 12.04 have been removed in 0.93.1 due to compatibility issues. Please use the offline bundles posted on the 0.92.3 tab, which is perfectly compatible when paired with an online computer using 0.93.1.** ## GPG-Verifying Armory Installers **Update:** If you already have a verified copy of Armory version 0.91 or higher, you can use the new secure downloader feature to get upgrades and/or installers for other systems. See the next section for more info. If you don't have a verified copy of Armory yet, you should follow these instructions to verify the first Armory installer you download via GPG. Armory is used by some of the most heavily-invested, and most paranoid Bitcoin enthusiasts and cloud miners 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)](http://pgp.mit.edu:11371/pks/lookup?search=bitcoinarmory+offline&op=index) (0x98832223). 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) <[email protected]>" $ dpkg-sig --verify *.deb > Processing armory_0.85-beta_amd64.deb... > GOODSIG _gpgbuilder 821F122936BDD565366AC36A4AB16AEA**98832223** 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 **4AB16AEA98832223**. The last set of digits (1353699840) is simply a timestamp indicating when the signature was made. This will be different for every new and can safely be ignored. ## Upgrading Armory Using The Secure Downloader (Version 0.91+) If you do not currently have any version of Armory installed or currently have a version older than 0.91, you should consider verifying the installers via GPG as described above. However, since version 0.91, we have integrated the "secure downloader" which retrieves download links and cryptographic signatures from our server, and verifies those cryptographic signatures for you. This can also be used to download installers for other systems. You can open the secure downloader via **Help > Update Software** from the main window. Make sure you select your operating system, OS version, and architecture (32 or 64-bit) before selecting your package. Furthermore, if you already have a copy of Armory 0.91+ on your offline computer, you can select the option "_Save with offline-verifiable signature_" before you click the "Download" button. This will save a ***.signed** file which is the regular installer with the cryptographic signatures bundled with it. If you choose this option, copy the *.signed file to the offline computer, and within Armory 0.91+ use **Help > Verify Signed Package.** If the digital signature is valid, then it will give you an opportunity to save the verified installer to disk. [1]: /images/download/key.png [2]: /images/download/lock.png [3]: /images/download/macosx.png [4]: /images/download/raspberrypi.png [5]: /images/download/ubuntu.png [6]: /images/download/windows.png