Re: you iso's may have been hacked

Hi, Andrew F Comly wrote: > Am I supposed to edit the script and put something in for magic=' '? No. Magic is what an ISO 9660 should bear at byte offset 32768: A byte with ASCII value 1 and five bytes saying "CD001": $ dd if=debian-8.4.0-amd64-netinst.iso bs=1 skip=32768 count=6 | od -c

Re: you iso's may have been hacked

Thomas Schmitt wrote: >Steve McIntyre wrote: >> It's also contained in the debian-role-keys keyring in the >> debian-keyring package: [...] >> and the full fingerprint is also on the Debian website using https for >> people who would rather trust that. > >We users could easily be outsmarted in

Re: you iso's may have been hacked

Hi, Steve McIntyre wrote: > It's also contained in the debian-role-keys keyring in the > debian-keyring package: [...] > and the full fingerprint is also on the Debian website using https for > people who would rather trust that. We users could easily be outsmarted in this aspect, i fear. It's

Re: you iso's may have been hacked

Thomas Schmitt wrote: >Hi, > >Andrew F Comly wrote: >> gpg: WARNING: This key is not certified with a trusted signature! > >I wonder whom we could trust to certify the Debian gpg key ... It's signed by a number of prominent DDs, including 2 DPLs and 2 Release Managers. Oh, and a number of idiots

Re: you iso's may have been hacked

Le 10/08/2016 à 08:36, Thomas Schmitt a écrit : Andrew F Comly wrote: Notice how the two sha512sum numbers (local vs burnt usb) don't match! Of course : the image and the device do not have the same size. Determine the ISO size on /dev/sdb by program isosize and curb its reading by help

Re: you iso's may have been hacked

Hi, Andrew F Comly wrote: > gpg: WARNING: This key is not certified with a trusted signature! I wonder whom we could trust to certify the Debian gpg key ... > Notice how the two sha512sum numbers (local vs burnt usb) don't match! Determine the ISO size on /dev/sdb by program isosize and curb

Re: you iso's may have been hacked

Hi, Doug wrote: > If the md5 sum doesn't agree with what's posted, it most likely means a > glitch in the data transmission. Download it again. Good advise. One has to be aware that MD5 is not considered to be safe against malicious manipulations but only for transport safety. If one has to

Re: you iso's may have been hacked

On 08/09/2016 08:37 PM, limpia wrote: On 2016-08-09 20:03, phil hall wrote: i have just downloaded debian gnome 8.5.0 when complete i clicked check MD5 sum it listed a number that's not in your MD5sum document. I have never checked an MD5sum, so don't know if this is a Mint bug or you've

Re: you iso's may have been hacked

On 08/09/2016 08:03 PM, phil hall wrote: i have just downloaded debian gnome 8.5.0 when complete i clicked check MD5 sum it listed a number that's not in your MD5sum document. I have never checked an MD5sum, so don't know if this is a Mint bug or you've been hacked If the md5 sum doesn't

Re: you iso's may have been hacked

On 2016-08-09 20:03, phil hall wrote: i have just downloaded debian gnome 8.5.0 when complete i clicked check MD5 sum it listed a number that's not in your MD5sum document. I have never checked an MD5sum, so don't know if this is a Mint bug or you've been hacked On 2016-08-09 20:24, limpia

Re: you iso's may have been hacked

On 2016-08-09 20:03, phil hall wrote: i have just downloaded debian gnome 8.5.0 when complete i clicked check MD5 sum it listed a number that's not in your MD5sum document. I have never checked an MD5sum, so don't know if this is a Mint bug or you've been hacked Thanks, but it would be a lot

you iso's may have been hacked

i have just downloaded debian gnome 8.5.0 when complete i clicked check MD5 sum it listed a number that's not in your MD5sum document. I have never checked an MD5sum, so don't know if this is a Mint bug or you've been hacked