Topic: Air-Gapped Armory on Bitkey (Read 91 times)
You could build Armory straight for the target OS as an alternative.
https://github.com/goatpig/BitcoinArmory/releases/tag/v0.96.3.992
This is a release candidate of an older version, idk why your guide is based on this. Use at your own peril.
This is a release candidate of an older version, idk why your guide is based on this. Use at your own peril.
Thanks goatpig, indeed the sha256sun does not match. My work around was to build Bitkey community from source but using the Armory binary version signed with your pgp key instead ..
I really like the project .. I am thinking about to write a simple bash script to cheksum all wallets binaries instaled at Bitkey against the original sources then make a pull request..
Btw I am not sure if "TurnKey Development Toolchain and Build System" (https://www.turnkeylinux.org/tkldev) has something like the guidances such as those I read on LinuxQuestions Forum:
Quote
Different distro have different specifics about what is involved in being a package maintainer.
Debian has the New Maintainers' Guide for their "DebianDevelopers." Fedora has a set of pages about joining the package collection maintainers. Arch lists their types of contributors. I'm sure there are as many methods of organizing the contributors as there are distros.
Debian has the New Maintainers' Guide for their "DebianDevelopers." Fedora has a set of pages about joining the package collection maintainers. Arch lists their types of contributors. I'm sure there are as many methods of organizing the contributors as there are distros.
but that is something I will be looking at.
https://github.com/goatpig/BitcoinArmory/releases/tag/v0.96.3.992
This is a release candidate of an older version, idk why your guide is based on this. Use at your own peril.
This is a release candidate of an older version, idk why your guide is based on this. Use at your own peril.
Hi,
I was playing around with bitkey community and since version 14.2.0 they added armory wallet
https://github.com/bitkey/bitkey/releases/tag/14.2.0-community-1.13
Looking the source code
\bitkey-14.2.0-community-1.13\bitkey-14.2.0-community-1.13\overlay\usr\local\src
I notice that they using
armory_0.96.3.992-gcc4.7_amd64.deb
that binary got sha256 fingerprint
6168185166B8D762A64888CAD9FEE69623744499AA9D1662E5CC6BC5415E6EA3
I could not find any match on
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
811982406b1c541eb06c2363d67a5c3d5ff367899a299325cd8342df02b7c461 armory_0.96.3-src.tar.gz
f05593c56f74b2e5a765f378cb279d981a5dedf305364eb0ab14836aacc6c104 armory_0.96.3-gcc4.7_amd64.deb
2ddb07ff5d8d19872e0b7547b5a90d0fe8da2d254d8e678b14c0eee9c4e31b98 armory_0.96.3-gcc5.4_amd64.deb
851f218b78dbf0acb84c111b8989254155828d8f9fdfa5ab21c25fda10745fdc armory_0.96.3_osx.tar.gz
6ebdba82adee495a3b4f2a1b4f923e07ef84855c2911b3abb9f832c721b98b02 armory_0.96.3_win64.exe
fe3d5bd4860d33c72831fe469df003ff66329fdff49084ec12af2b5f2e388a90 armory_0.96.3_win64.zip
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBCAAGBQJZxTtHAAoJEIxSEXZJIlia770P/R2kBI3DrkSYRyXvqGbMHuX4
Mljv6hTiaPEa08DhY23l2l3yqAYjLDEvL5hX+TwQA2BnUghj+KgZ8K1zdIOId7vW
SO+DwMgxTWOv2GTxVixV689f8AfcuxYmiaWsDplnK0kxz5mfH+jo5TYXlLxxy4L9
xDcLHyFpFed+PVgdf4yRn9snwcqTkZj/B4NzS3PzPShQzg1MjoGw7QDlv6Go7msr
p0cqIPsSx2lhVZM42e75+5XXbOqmczvQwpEXnHkbapX24gFagCbjhRIDL41kIpjJ
tk/P/CxaOv2tjDBsQgTZm9Jb7NY67EEpqIg9SvAPgNSYUPJnIGmeraCXH31XSq3o
JmPNvUJcR03nokIxdVEOTRzFrKdJpX2SM5sBB5j18Y0iXcHBVJRKZlzZlS4VPh4b
4gjgRBYo/ctPhlXYfUM5sdcvAoubamQNvlD1ONNocFB15+t+bxBNsc0arfAZDNEm
e56flxXHuF9BFfCfatxKMz4z4ChakdMTMtnpfnLkSXe0OX2+BRLEoxrQI8+aFJxv
9O950O19qipHTAs8rKXy5IgHpm7we8Vo+FORe+o1ZxwhIJf9tiZTxAGYcGCX9JMX
lYvE8fGvxpPbIYFesAAbJS8eUaQkiZ1rYpaO8LdG3BmvT3779YNMBjYUXvrly7F7
3uI2cQmQCTQUOk5FHMYv
=bbl5
-----END PGP SIGNATURE-----
is there any other way to verify that file (or that particular version?)
I was playing around with bitkey community and since version 14.2.0 they added armory wallet
https://github.com/bitkey/bitkey/releases/tag/14.2.0-community-1.13
Looking the source code
\bitkey-14.2.0-community-1.13\bitkey-14.2.0-community-1.13\overlay\usr\local\src
I notice that they using
armory_0.96.3.992-gcc4.7_amd64.deb
that binary got sha256 fingerprint
6168185166B8D762A64888CAD9FEE69623744499AA9D1662E5CC6BC5415E6EA3
I could not find any match on
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
811982406b1c541eb06c2363d67a5c3d5ff367899a299325cd8342df02b7c461 armory_0.96.3-src.tar.gz
f05593c56f74b2e5a765f378cb279d981a5dedf305364eb0ab14836aacc6c104 armory_0.96.3-gcc4.7_amd64.deb
2ddb07ff5d8d19872e0b7547b5a90d0fe8da2d254d8e678b14c0eee9c4e31b98 armory_0.96.3-gcc5.4_amd64.deb
851f218b78dbf0acb84c111b8989254155828d8f9fdfa5ab21c25fda10745fdc armory_0.96.3_osx.tar.gz
6ebdba82adee495a3b4f2a1b4f923e07ef84855c2911b3abb9f832c721b98b02 armory_0.96.3_win64.exe
fe3d5bd4860d33c72831fe469df003ff66329fdff49084ec12af2b5f2e388a90 armory_0.96.3_win64.zip
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBCAAGBQJZxTtHAAoJEIxSEXZJIlia770P/R2kBI3DrkSYRyXvqGbMHuX4
Mljv6hTiaPEa08DhY23l2l3yqAYjLDEvL5hX+TwQA2BnUghj+KgZ8K1zdIOId7vW
SO+DwMgxTWOv2GTxVixV689f8AfcuxYmiaWsDplnK0kxz5mfH+jo5TYXlLxxy4L9
xDcLHyFpFed+PVgdf4yRn9snwcqTkZj/B4NzS3PzPShQzg1MjoGw7QDlv6Go7msr
p0cqIPsSx2lhVZM42e75+5XXbOqmczvQwpEXnHkbapX24gFagCbjhRIDL41kIpjJ
tk/P/CxaOv2tjDBsQgTZm9Jb7NY67EEpqIg9SvAPgNSYUPJnIGmeraCXH31XSq3o
JmPNvUJcR03nokIxdVEOTRzFrKdJpX2SM5sBB5j18Y0iXcHBVJRKZlzZlS4VPh4b
4gjgRBYo/ctPhlXYfUM5sdcvAoubamQNvlD1ONNocFB15+t+bxBNsc0arfAZDNEm
e56flxXHuF9BFfCfatxKMz4z4ChakdMTMtnpfnLkSXe0OX2+BRLEoxrQI8+aFJxv
9O950O19qipHTAs8rKXy5IgHpm7we8Vo+FORe+o1ZxwhIJf9tiZTxAGYcGCX9JMX
lYvE8fGvxpPbIYFesAAbJS8eUaQkiZ1rYpaO8LdG3BmvT3779YNMBjYUXvrly7F7
3uI2cQmQCTQUOk5FHMYv
=bbl5
-----END PGP SIGNATURE-----
is there any other way to verify that file (or that particular version?)
Jump to: