search

Raptor3um / raptoreum

MIT License
316 stars 132 forks source link

Releases description mention sha256 instead of sha1 #302

Open leovbernardo opened 1 year ago

leovbernardo commented 1 year ago

All references to "sha256" checksums in the [1.3.17.05] (https://github.com/Raptor3um/raptoreum/tree/1.3.17.05) and [1.3.17.04] (https://github.com/Raptor3um/raptoreum/tree/1.3.17.04) releases should be "sha1", instead.

This may trigger people to think that the files are unsafe to use.

michal-zurkowski commented 1 year ago

+1 The current SHA256 in release is SHA1 in actuality. SHA256-openssl should be just renamed to SHA256.

Imo SHA1 hashes should be removed altogether. SHA1 is no longer considered secure, and its vulnerabilities make it easier for attackers to perform malicious activities. SHA256 provides better security and is the recommended hash function.