Please include an SHA256 hash of the Cabal file itself about all-cabal-hashes HOT 5 CLOSED

That's going to significantly increase the download size, which will affect
end users using this repo. I also don't think it adds any security to have
the checksum in the same location as the original file: anyone who can
compromise the latter can compromise the former too.

On Fri, Sep 18, 2015, 12:50 PM Peter Simons [email protected]
wrote:

When building these packages in Nix, we need to download the modified
Cabal file in case the package has underdone revisions after the upload.
This means that we need to know a checksum of the Cabal file in addition to
the one we already have for the release tarball. It would be great if that
hash would be included in this repository.

—
Reply to this email directly or view it on GitHub
#4.

from all-cabal-hashes.

The change is not intended to improve security. It's just intended to make use of the JSON files more convenient.

from all-cabal-hashes.

I'm not understanding the value this would add, since the checksum will be sitting right next to the .cabal file itself, and therefore calling sha256sum on that file would have the same effect.

from all-cabal-hashes.

It's just a matter of convenience. I parse the foo.json file to get all meta information about the Cabal file that I need, i.e. it contains various hashes of the package tarball. The only thing it doesn't contain is the hash of the Cabal file itself. I know it's trivially computable given the Cabal file, but in my code it would be easier if I wouldn't have to bother computing it.

from all-cabal-hashes.

I'm not seeing this as compelling enough, sorry. Users would end up having do download two new blobs for every revised cabal file instead of one. We have the very nice property right now that the .json files are immutable for each package/version combo, and I don't want to lose that.

from all-cabal-hashes.