Originally Posted by
steev
Hey Alexus,
Thanks for the report - despite the image corruption with --test, the image still worked, and tools like pixz were extracting it (what is used to create the image);
That said, I've generated a new 2017.1.1 image and added unxz --test to one of the test suite that gets run when images are generated so that this doesn't occur in the future. They should be up on the mirrors now.
If you have any more issues please let me know!
Thank you for getting back to me, per your comment I gave it a try and it seems to be fine now:
Code:
$ wget https://images.offensive-security.com/arm-images/kali-2017.01-veyron.img.xz
--2017-06-08 15:41:33-- https://images.offensive-security.com/arm-images/kali-2017.01-veyron.img.xz
Resolving images.offensive-security.com (images.offensive-security.com)... 192.99.63.209, 198.255.36.10, 199.189.86.7, ...
Connecting to images.offensive-security.com (images.offensive-security.com)|192.99.63.209|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1138130500 (1.1G) [application/x-xz]
Saving to: ‘kali-2017.01-veyron.img.xz’
100%[============================================================>] 1,138,130,500 778KB/s in 22m 48s
2017-06-08 16:04:21 (812 KB/s) - ‘kali-2017.01-veyron.img.xz’ saved [1138130500/1138130500]
$ sha256sum kali-2017.01-veyron.img.xz
f36865ece710f097ee92551db424535738f2c5e61226956752f1417064608f5e kali-2017.01-veyron.img.xz
$ unxz --test kali-2017.01-veyron.img.xz
$ echo $?
0
$