we want : a7c0afe862f6ea19a596801fc138bde0463abcbce1b753e8d5c474b506a2db2d
we get:
1 Like
dear dave_WOODS.
Thank you for posting.
We are currently starting to evaluate the results of sha256sum.
There are two types of sha256sum: Python code and Linux core tool code.
To isolate the problem, I’m doing the verification in Python code. This is because Anaconda’s basic commands are written using Python code.
If it is a download from a disguised site, we think that we are in a very dangerous situation.
Thank you for your continued support.
ktsh.tanaka.2020
Hi,
Update Update,
I have re-downloaded the file, I have been able to obtain an expected sha256sum the standard way (linux-core non-binary).
I apologise yet something remains to reveal,
my alert was most likely caused by interrupted downloads,
the question remains.
THIS IS NOT, SPEAKING FOR THE IDENTICAL PROBLEM RAISED AT THE LINK POSTED EARLIER.
wait… this does remain to be solved: half / broken downloads should give different sha256sum anyway, to the next: here we have a sha256sum for different broken downloads giving identical results from a version to the next on different locations of the world.
Generally speaking, I support your view of permanent sha256sum tracking from positions around the world: this WOULD be a very dangerous situation.
Have a lovely day,
Dave.