Re:Go 1.14 release notes
by mfer on Tuesday February 25, 2020 @02:42PM
(#22416595)
It just struck me that the Go team does not provide PGP or other cryptographic signing/verification of releases.
[ Parent
| on HN ]
They have checksum hashes but not crypto verifiable signatures.
$ curl https://dl.google.com/go/go1.13.4.src.tar.gz.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAABCAAGBQJdu22LAAoJEGSUxtaZfCFeXigQAKc6NflWvvbaZ6S7RCVuRNzA
...Nice. Thanks for sharing. I didn't see that documented. Would be great to have it documented.
Re:Go 1.14 release notes
by shawabawa3 on Tuesday February 25, 2020 @02:46PM
(#22416639)
What assurances does that give you beyond the https certificate on their official website which contains the binary downloads and hashes?
Defense in depth, essentially. But yes, checking site X to see if site X gave you Y correctly is rather weak confidence.
To argue in its favor tho, file-hosting and site-serving may be handled by different systems with different security characteristics, and potentially even different datacenters (e.g. a CDN). If you only have to compromise one system, it's generally easier to do so than when you have to compromise N and make them all agree with each other.
The hash and file are not hosted on the same place so it's good enough.
If a hosting server is compromised the hash and download can be changed with something nefarious. crypto signing/verification will catch that case. hash checking will not.
This is a legitimate case as it's happened to other projects in the past.
Re:Go 1.14 release notes
by groobongithub on Tuesday February 25, 2020 @03:14PM
(#22416947)
The download comes from dl.google.com while the checksum is published on golang.org.
FWIW the macOS pkg you download is signed.