Skip to contentSkip to conversation

wireguard-tools-1.0.20210914.tar.xz hash changed

DISCUSSION Peter Korsgaard 3 participants 7 messages Aug 26, 2024

lore
Share & tools
lore
#0 lore raw

Hi Jason,

Did you recently upgrade xz on git.zx2c4.com? I see that the hash of wireguard-tools-1.0.20210914.tar.xz changed:

http://autobuild.buildroot.org/results/d63b8f5b14487f6d79c9779bb7fe4829fae0653b/build-end.log

We have a backup of the original file on sources.buildroot.net:

mkdir a b
wget -q -P a https://git.zx2c4.com/wireguard-tools/snapshot/wireguard-tools-1.0.20210914.tar.xz
wget -q -P b https://sources.buildroot.net/wireguard-tools/wireguard-tools-1.0.20210914.tar.xz

sha256sum */*
942ed32d1d6631932c82ff86c91ae8428d4c90bfec231a14ebdf6c29f068e60b a/wireguard-tools-1.0.20210914.tar.xz 97ff31489217bb265b7ae850d3d0f335ab07d2652ba1feec88b734bc96bd05ac b/wireguard-tools-1.0.20210914.tar.xz

The uncompressed tarball is identical:

unxz */*xz
sha256sum */*tar
22d6d0b12ec69be002313a89dbe2c08c07d48c5b93af528189ceab351b3b718d a/wireguard-tools-1.0.20210914.tar 22d6d0b12ec69be002313a89dbe2c08c07d48c5b93af528189ceab351b3b718d b/wireguard-tools-1.0.20210914.tar

It would be great if we could have a bit-identical .tar.xz.

Signature · 1 line
Bye, Peter Korsgaard
#1 lore raw
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Peter" == Peter Korsgaard <[email protected]> writes:

Hello Jason,

Was this change done on purpose?

Quoted 32 lines

Hi Jason,
Did you recently upgrade xz on git.zx2c4.com? I see that the hash of wireguard-tools-1.0.20210914.tar.xz changed:

http://autobuild.buildroot.org/results/d63b8f5b14487f6d79c9779bb7fe4829fae0653b/build-end.log

We have a backup of the original file on sources.buildroot.net:

mkdir a b
wget -q -P a
https://git.zx2c4.com/wireguard-tools/snapshot/wireguard-tools-1.0.20210914.tar.xz
wget -q -P b https://sources.buildroot.net/wireguard-tools/wireguard-tools-1.0.20210914.tar.xz

sha256sum */* 942ed32d1d6631932c82ff86c91ae8428d4c90bfec231a14ebdf6c29f068e60b a/wireguard-tools-1.0.20210914.tar.xz 97ff31489217bb265b7ae850d3d0f335ab07d2652ba1feec88b734bc96bd05ac b/wireguard-tools-1.0.20210914.tar.xz

The uncompressed tarball is identical:

unxz */*xz
sha256sum */*tar 22d6d0b12ec69be002313a89dbe2c08c07d48c5b93af528189ceab351b3b718d a/wireguard-tools-1.0.20210914.tar 22d6d0b12ec69be002313a89dbe2c08c07d48c5b93af528189ceab351b3b718d b/wireguard-tools-1.0.20210914.tar

It would be great if we could have a bit-identical .tar.xz.

Signature · 1 line
Bye, Peter Korsgaard
Signature · 1 line
Bye, Peter Korsgaard
#2 lore raw
In reply to Peter Korsgaard
Quoted 18 lines · Peter Korsgaard

Hi Jason,

Did you recently upgrade xz on git.zx2c4.com? I see that the hash of wireguard-tools-1.0.20210914.tar.xz changed:

http://autobuild.buildroot.org/results/d63b8f5b14487f6d79c9779bb7fe4829fae0653b/build-end.log

We have a backup of the original file on sources.buildroot.net:

mkdir a b
wget -q -P a https://git.zx2c4.com/wireguard-tools/snapshot/wireguard-tools-1.0.20210914.tar.xz
wget -q -P b https://sources.buildroot.net/wireguard-tools/wireguard-tools-1.0.20210914.tar.xz

sha256sum */*
942ed32d1d6631932c82ff86c91ae8428d4c90bfec231a14ebdf6c29f068e60b a/wireguard-tools-1.0.20210914.tar.xz 97ff31489217bb265b7ae850d3d0f335ab07d2652ba1feec88b734bc96bd05ac b/wireguard-tools-1.0.20210914.tar.xz

Quoted 8 lines

The uncompressed tarball is identical:

unxz */*xz
sha256sum */*tar
22d6d0b12ec69be002313a89dbe2c08c07d48c5b93af528189ceab351b3b718d a/wireguard-tools-1.0.20210914.tar 22d6d0b12ec69be002313a89dbe2c08c07d48c5b93af528189ceab351b3b718d b/wireguard-tools-1.0.20210914.tar

It would be great if we could have a bit-identical .tar.xz.

I updated xz on the system. Bah, that's annoying.

I've downgraded it now and the hash should check out. But this issue is sure to come up again in the future....

Jason

#3 lore raw
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Jason" == Jason A Donenfeld <[email protected]> writes:

Hi Jason,

Quoted 6 lines
Quoted 1 line

It would be great if we could have a bit-identical .tar.xz.

I updated xz on the system. Bah, that's annoying.

I've downgraded it now and the hash should check out. But this issue is sure to come up again in the future....

Thanks! I've verified that it is indeed correct again. Out of interest, what xz versions were this about exactly?

For Buildroot I will have a look at moving these autogenerated / snapshot downloads to the .tar.gz variant that is probably more stable over versions.

Signature · 1 line
Bye, Peter Korsgaard
#4 lore raw
Quoted 7 lines · Peter Korsgaard
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

"Jason" == Jason A Donenfeld <[email protected]> writes:

Hi Jason,

Quoted 1 line
Quoted 1 line

It would be great if we could have a bit-identical .tar.xz.

Quoted 7 lines
Quoted 4 lines

I updated xz on the system. Bah, that's annoying.

I've downgraded it now and the hash should check out. But this issue is sure to come up again in the future....

Thanks! I've verified that it is indeed correct again. Out of interest, what xz versions were this about exactly?

I downgraded from the latest one to the one that existed before Jia Tan appeared.

Quoted 3 lines

For Buildroot I will have a look at moving these autogenerated / snapshot downloads to the .tar.gz variant that is probably more stable over versions.

Long term I intend to move everything over to .zst, I think.

#5 lore raw
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Jason" == Jason A Donenfeld <[email protected]> writes:

Hi,

Quoted 5 lines
Quoted 3 lines

For Buildroot I will have a look at moving these autogenerated / snapshot downloads to the .tar.gz variant that is probably more stable over versions.

Long term I intend to move everything over to .zst, I think.

OK. Do you have reasons to expect .zst output to be bit identical between versions? It presumably means that the compression ratio can not improve over time, hence my suggestion for a legacy format like .gz.

The trigger for all of this is the on the fly snapshot generation from cgit. How about archiving the snapshot tarballs somewhere permanent instead?

Signature · 1 line
Bye, Peter Korsgaard
#6 lore raw
In reply to Jason A. Donenfeld

Hi,

FWIW I did a manual byte-for-byte comparison between the two files last week and the change is that the newer version adds two more headers; one for compressed file size, and one for uncompressed file size. The values encoded therein are correct as well. As per the xz specification they are included to aid decompression software.

Regards,

Kim Nilsson

Quoted 20 lines · Jason A. Donenfeld
Quoted 5 lines · Peter Korsgaard
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Jason" == Jason A Donenfeld <[email protected]> writes:

Hi Jason,

Quoted 1 line
Quoted 1 line

It would be great if we could have a bit-identical .tar.xz.

Quoted 7 lines
Quoted 4 lines

I updated xz on the system. Bah, that's annoying.

I've downgraded it now and the hash should check out. But this issue is sure to come up again in the future....

Thanks! I've verified that it is indeed correct again. Out of interest, what xz versions were this about exactly?

I downgraded from the latest one to the one that existed before Jia Tan appeared.

Quoted 3 lines

For Buildroot I will have a look at moving these autogenerated / snapshot downloads to the .tar.gz variant that is probably more stable over versions.

Long term I intend to move everything over to .zst, I think.