|
Boost : |
Subject: Re: [boost] Boost 1.61.0 Beta 1 Release Candidate 2
From: Vladimir Prus (vladimir.prus_at_[hidden])
Date: 2016-03-24 15:34:51
On 03/23/2016 10:29 PM, Vladimir Prus wrote:
> The SHA256 checksums are as follows:
>
> bc8341bfb8c6621319ad9eb732179fc7ec4da35c3cefc31b613f83ec3df10361 boost_1_61_0_b1_rc2.7z
> c0f06c78c195af9079773a2b250674244f1899ec81e84d5455f0761f1d888a16 boost_1_61_0_b1_rc2.tar.bz2
> 400fa0949aa201d993bf116461365e5d44904a3f8db6412f4f40f2b4ab490405 boost_1_61_0_b1_rc2.tar.gz
> d75688ecad601303dda2658e9a3d06f406dd4dc8e2c13c36bdadcac0a11dcffa boost_1_61_0_b1_rc2.zip
Since there were requests that we sign releases in some way, I wanted to beta test that.
Attached is a list of checksums signed by my personal GPG key. The key can be found at:
https://pgp.mit.edu/pks/lookup?op=get&search=0xDA472E8659753BA4
or
https://vladimirprus.com/vladimir.prus.gpg
The key fingerprint is:
C5F0 F367 AA66 616F B839 806E DA47 2E86 5975 3BA4
I would appreciate if folks confirm that this information is sufficient to validate checksums.
Thanks,
-- Vladimir Prus http://vladimirprus.com
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk