Development release newLISP v.10.7.4

[Kirill]

What is the correct SHA1 checksum for the release? In http://www.newlisp.org/downloads/development/SHA1.txt">http://www.newlisp.org/downloads/development/SHA1.txt it says

SHA1(newlisp-10.7.4.tgz)= 5a3ce129f43138773abdc479a03512699e8a4256

But I'm getting a different SHA1 when fetching tgz myself:

Code Select Expand


km ~/src $ ftp http://www.newlisp.org/downloads/development/newlisp-10.7.4.tgz
Trying 208.94.116.177...
Requesting http://www.newlisp.org/downloads/development/newlisp-10.7.4.tgz
100% |**********************************************************************|  1148 KB    00:02
1176073 bytes received in 2.79 seconds (412.26 KB/s)
km ~/src $ sha1 newlisp-10.7.4.tgz
SHA1 (newlisp-10.7.4.tgz) = 7b4e1f84d878a101dbe761fdd68bbfafe819e9f9


[rickyboy]

Kirill, I get the same:

Code Select Expand

$ uname -rsm
FreeBSD 12.0-RELEASE amd64
$ fetch http://www.newlisp.org/downloads/development/SHA1.txt
$ fetch http://www.newlisp.org/downloads/development/newlisp-10.7.4.tgz
$ cat SHA1.txt; sha1 newlisp-10.7.4.tgz
SHA1(newlisp-10.7.4.tgz)= 5a3ce129f43138773abdc479a03512699e8a4256
SHA1 (newlisp-10.7.4.tgz) = 7b4e1f84d878a101dbe761fdd68bbfafe819e9f9


[Lutz]

Oops, not sure how this happened.



On my development computer: 7b4e1f84d878a101dbe761fdd68bbfafe819e9f9



So the newlisp-10.7.4.tgz checksum is correct but the SHA1.txt is wrong and has been updated now.

[rickyboy]

Thanks, Lutz!  And thanks to Kirill for finding this!

[Kirill]

Thank you, both! Good to know that it wasn't someone trying to hijack systems running newLISP. :)