-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

md5:
3613b1e032d878f162876e61acebe5b7
sha1:
1f3b5c0a51ab4772e8b68ed3ee25386f8fe8dc2e
sha256:
045c8b9fbbbcaaed3486f2819f9a3d9256cd75b603f6579ea1efca16f0ef6383
sha512:
d953f92481a2cbe0371f5666aaa4bff6e725234d7a5b21185fcc9596c33a4add62b09e4ce01b2f4ff87345dc3d7283056e3114ef130c7ea8af6c642ac5fcacfd

Use https://www.quickhash-gui.org/ to verify file integrity hashes in Windows
or you can use the built-in certutil command as described on https://cryptostorm.is/windows

If you're concerned about us using weak algorithms here like md5 and sha1, there's no way to collide md5 and sha1 at the same time.
I.e., you could do a collision with just md5, but that would change the sha1, or vice versa.
That's why you should be checking all 4 hashes, or at least the sha256/512 ones. The md5/sha1 sums are more for CRC than security.
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEETYf5hKIig5JX/jalu9uZGunHyUIFAmqYlroACgkQu9uZGunH
yUJ09w/9FSUePNyI6r5NlSnMpAWuKX3eA3s5RG+AsbLv0jxciL/LByZFxTwkzibG
uJBNIJgDZigu+bCMmSEGG8NA0CunblQPAXBAZMSCws4SIgpAhadBluryk8wmTdh3
/Jsrv1NfCIhTlPH/0MFTuDqDw7mpa64JZEWJdAETY8sKZi/waGbyXIbdsqC2hrB+
VzfRicawwdSCoFYo7srR1nAnApE9feFFxJVsnGoqfw+yHzmy55k1wDr7NAdDpWmi
Ss/A2DaDzdBrQ3Kb5042qncBQrSxvhlshag8ROmL+73ksDxV71w3AQEAEGonJ7kn
1kIFl1DKkRNHMJlqoznsLnH5n+txS02p+C0stKCGT7aC+5t5q8PiH9zVSECxVhBn
rRWtllXm6QBPyZppVvMX3LNkzUfs4WElChG7BRoJwhIiT90l2Bw97+f/8XLJKM2T
+qvSOJPO+s1bj3hFLyb3feF3Ybj9tYu1qbb/VUWs7NaP+55EcCxv5X8/Zc5YyvvN
Zih/81gm03UFL/iYf02nrwJKkCKs7XY11rxq7YkCRdhtWkLNegwE+EuGlbw621rH
H4JmVmVZWpcIsA3ZzVwdQH7HNYmXm1LUkPW2lsUewru1jfb0MaZ7P5MrtU57v7ik
bhI1/w6aql8NfmSOcNy/nTKPUvTOP7iuqZ+O9Anngs+qqzAMBL4=
=68AG
-----END PGP SIGNATURE-----