From b46ca76dbc121d652fa4ba07e81b409c9c88b10b Mon Sep 17 00:00:00 2001 From: BashCo Date: Fri, 19 Aug 2016 14:29:16 +0200 Subject: [PATCH] Update 2016-08-17-binary-safety.md Slightly softer language in the last 3 sentences. --- _alerts/2016-08-17-binary-safety.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/_alerts/2016-08-17-binary-safety.md b/_alerts/2016-08-17-binary-safety.md index 8b6ee465..c8bc8b9d 100644 --- a/_alerts/2016-08-17-binary-safety.md +++ b/_alerts/2016-08-17-binary-safety.md @@ -24,6 +24,6 @@ are most at risk here due to the origin of the attackers. The hashes of Bitcoin Core binaries are cryptographically signed with [this key](https://bitcoin.org/laanwj-releases.asc) belonging to Bitcoin Core maintainer Wladimir J. van der Laan. Additional signatures from other developers can be found in the [gitian signatures repository](https://github.com/bitcoin-core/gitian.sigs). -We strongly recommend that you download Wladimir's key from multiple sources in addition to Bitcoin.org for comparison purposes. For example, you can cross reference Bitcoin.org's copy with the [bitcoin-dev mailing list](https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-June/009045.html) where Wladimir signed a message containing the key's fingerprint (01EA5486DE18A882D4C2684590C8019E36C2E964), but we encourage you to seek out other sources as well in order to make sure you are verifying your download with the correct key. Furthermore, we strongly recommend verifying your download using signatures from multiple developers using the gitian signatures repository. +We strongly recommend that you download Wladimir's key from multiple sources in addition to Bitcoin.org for comparison purposes. For example, you can cross reference Bitcoin.org's copy with the [bitcoin-dev mailing list](https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-June/009045.html) where Wladimir signed a message containing the key's fingerprint (01EA5486DE18A882D4C2684590C8019E36C2E964), but we encourage you to seek out other sources as well in order to make sure you are verifying your download with the correct key. Furthermore, we recommend verifying your download using signatures from multiple developers using the gitian signatures repository. -You should securely verify multiple signatures and hashes before running any Bitcoin Core binaries. This is the safest and most secure way of being confident that the binaries you're running are the same ones created by the Core Developers. +It is always best practice to securely verify multiple signatures and hashes before running any Bitcoin Core binaries. This is the safest and most secure way to ensure that the binaries you're running are the same ones created by the Core Developers.