in the past the opensuse 13.2 .iso images had md5sum, so, using k3b I can easily check the md5sum copying the md5sum in the file downloaded by suse, now I downloaded leap42.1 and its sha256, but I cannot do the same as 13.2 becouse I haven’t the md5sum and k3b gives only the md5sum.
is there an as easy and newby like in the past way to check and compare sha256???
manythanks ciao pier
“sha256sum” will check the sha256 checksum.
I normally use:
wget path-to-image.iso.sha256
aria2c -V path-to-image.iso
gpg --verify image.iso.sha256
sha256sum image.iso.sha256
Once you have verified the download, you can then compute the MD5 checksum yourself if you want to make use of the ability of k3b to check that. I “burn” to USB flash drives, so I don’t use k3b.
Thank you very much but I asked for “an as easy and newby as in the past way to check and compare sha256”, sha256sum gives a very long string, may be I succeed to compare it with the downloaded one, but it is too difficult for my newby sister… …in the past I told her to copy the string in the downloaded file, launch k3b, when k3b finished to check and the md5sum was shown rightclick on it and choose compare checksum, …is there a as simple as this way ??
Oops. The last of my suggested commands should have been:
sha256sum -c image.iso.sha256
The “-c” option tells “sha256sum” to compare the sum in the sha256 file with the computed checksum.
Yes, I agree that checking a long string of characters is not the best way of doing this. Let the software do the compare.
If I only have the announced sum, I would copy/paste into a file, and again use “sha256sum -c” to have the software do the compare.
if you download using KGet it will check the sha256 on download completion.
But I guess you have already downloaded the iso -so perhaps not helpful for this occasion.
manythanks, at first I didn’t understand that the image file and the sha256sum file had to have the same name except for the .sha256 at the end, got this it resulted enough simple for me and for my sister
The names don’t have to relate that way.
Inside the “.sha256” file, there is a line:
long-string-of-hex-digits filename
When you run “sha256sum -c”, it gets the filename to check from that line.
…ah, good to know manythanks again