busterrr3x Posted September 24, 2020 Posted September 24, 2020 (edited) BUSTER DESKTOP - GLOBAL: https://www.armbian.com/orange-pi-plus-2e/#kernels-archive-all I downloaded this on 2 different computers and got a bad checksum when I ran "sha256sum name.img". Wondering if anyone else is as well? I may have remote access malware on my computer - could be causing it somehow, possibly. Thanks. Edited September 25, 2020 by busterrr3x
Igor Posted September 24, 2020 Posted September 24, 2020 10 minutes ago, busterrr3x said: BUSTER DESKTOP - GLOBAL: https://www.armbian.com/orange-pi-plus-2e/#kernels-archive-all I downloaded this on 2 different computers and got a bad checksum when I ran "sha256sum name.img". Wondering if anyone else is as well? I may have remote access malware on my computer - could be causing it somehow, possibly. Thanks. Latest images are indeed corrupted - also decompressing is failing. I picked random older version from the archive and decompress alright, SHA is correct. Well, good that we have it but ... here we go again
busterrr3x Posted September 24, 2020 Author Posted September 24, 2020 Thanks Igor. Where would I get an older archived version?
Igor Posted September 24, 2020 Posted September 24, 2020 12 minutes ago, busterrr3x said: Where would I get an older archived version? Search for "Archived versions" on that page. Impossible to miss. At least I though so until now
busterrr3x Posted September 24, 2020 Author Posted September 24, 2020 Thanks - it's at the bottom of the page. 1
Igor Posted September 24, 2020 Posted September 24, 2020 Also I started: for archive in $(find ${STARTDIR} -name '*.xz'); do xz -tv $archive [[ $? -ne 0 ]] && exit 1 [[ $(sha256sum $archive | cut -d" " -f1) != $(cat ${archive}.sha | cut -d" " -f1) ]] && exit 1 done on our archive to see if the problem is at our side.
busterrr3x Posted September 24, 2020 Author Posted September 24, 2020 On 9/24/2020 at 5:40 PM, Igor said: Also I started: for archive in $(find ${STARTDIR} -name '*.xz'); do xz -tv $archive [[ $? -ne 0 ]] && exit 1 [[ $(sha256sum $archive | cut -d" " -f1) != $(cat ${archive}.sha | cut -d" " -f1) ]] && exit 1 done on our archive to see if the problem is at our side. I haven't checked the archives yet, so I was only saying I had a bad download with the main page. But thanks.
busterrr3x Posted September 25, 2020 Author Posted September 25, 2020 (edited) On 9/24/2020 at 6:04 PM, busterrr3x said: I haven't checked the archives yet, so I was only saying I had a bad download with the main page. But thanks. Sorry I don't fully understand the coding above, but I can see you were using shasum to check the archive images. Thanks. I checked my archive download and it checked out! QUESTION: I downloaded the BUSTER image (19.11.6 / 5.4.8) .img. In my .GNUPG directory, there is only an empty 'private keys' directory. Is this supposed to be like this or should there be 2 'text' documents next to the 'private keys' directory? One of my former buster downloads from a year ago or so, I know there were 2 simple text documents in the .gnupg directory. I am trying to learn how to send an encrypted message using gpg, but haven't been successful, yet. I was thinking that maybe there is a problem with my .gnupg directory and this is why I'm running into a snag with it. Thank you. Edited September 25, 2020 by busterrr3x clarify
Recommended Posts