sha3-384 mismatch

Michael Vogt michael.vogt at canonical.com
Fri Dec 2 16:52:39 UTC 2016


On Fri, Dec 02, 2016 at 02:32:03PM +0100, David Barth wrote:
> On Fri, Dec 2, 2016 at 1:04 PM, Pegenaute Bresme, Xavier <
> xpegenautebr at iam.cat> wrote:
[..]
> > - Download snap "snapweb" (25) from channel "stable" (sha3-384 mismatch
> > downloading snapweb: got 8b83c8eb7f7aa306bc342fd1b424fa
> > 95ccf379c068c4735085bc81ee6b51bb02a23b8c3c2a34f842619d7650b3152787 but
> > expected d0e1cd6d578c8eaab13e10dac4acbd7e8f6337da45b291fa7ae0358a2939
> > 3059732b29bb61a65d18e693b8e6e8a53b62)
> >
> 
> What is surprising is the "expected" signature.
> Snap is downloading the correct armhf build for 0.21.2, ie #25, and the
> SHA3 it obtained corresponds to the published version.

This version of snapd has a mixup of expected vs actual hash, this is
fixed in git. Sorry for the confusion.

I would love to see the actual file that got downloaded, that is
probably tricky because currently we delete those iirc. It would be
good to have the file to see if its garbage or a mostly valid squashfs
with some garbage in between or something else. Also size would be
interessting etc. 

Cheers,
 Michael




More information about the Snapcraft mailing list