Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Each release anouncement should have the signed sha hashes of the files #15

Closed
graingert opened this Issue Jan 28, 2012 · 1 comment

Comments

Projects
None yet
2 participants
Contributor

graingert commented Jan 28, 2012

eg:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

25c3ec9683d62235afea24d4a147d4616d8a884f  bitcoin-0.4.0-linux.tar.gz
a800d9fa4aa61527e598708f4ace7f855c22a46b  bitcoin-0.4.0-macosx.dmg
1d2c8d82ede5e8aa9f83b59da07e443de89c5c8f  bitcoin-0.4.0-src.tar.gz
ecf1304ff467bd30dc668b3dadff3044c3c86df1  bitcoin-0.4.0-win32-setup.exe
6034efe23e4bd76b0860f633e81710cd66d499db  bitcoin-0.4.0-win32.zip
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)

iEYEARECAAYFAk58n20ACgkQdYgkL74406ibEACgzyZj86lsQORi5HTs/N3ABCes
Pg8AoKFXU1vxiZI9qZOQ5ZET60ewcynW
=sY+Q
-----END PGP SIGNATURE-----
Contributor

saivann commented Oct 6, 2013

Release signatures are now displayed on the download page. They are also visible from the sourceforge download page linked on each release notes. So basically, they are visible each time a user chooses to download the files. I think this should be good enough for now.

@saivann saivann closed this Oct 6, 2013

jl2012 pushed a commit to jl2012/bitcoin.org that referenced this issue Apr 5, 2016

Merge pull request #15 from btcdrak/lic
Update CONTRIBUTING.md with licensing information
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment