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

md5:
365c280c6cd21a0a0f1b7b1e47cc7e7d
sha1:
1c33f9a2f49d36677e8fa9d5e22de34d094b7534
sha256:
afa4f567f60fa5cf2ae4832c50f475cd98c79d40e8d4479083139ea7e53a8b0f
sha512:
9759cf59707b7f6f315f59661c48d8fc147fb3b50c65ae4ffb2997563bc8c7cedbdb65639fc0fd7ae9cfe849f9bf3c9895cce5de5d56335c7920db83a6763930

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/jalu9uZGunHyUIFAmnWzvYACgkQu9uZGunH
yUJpsA/+Md9m39B0aJw9s8MYgw63bXeIWyGtktJ7XE05vY6eXPAq5qlGauyhJt7S
vpUVEUAzolEWGnz2cM7TdJYBEhBZrJPmQZUwPa/iWD+p4ztj+KSwcnhuT/lL+D/u
5SEqRr0q9APrfvXypPdEo9lYHYl0CnGqF0D6qSuePeuHvLZYY1IsyCLOdle7o3iC
MSvPQ6u8TXA4vzAxa/m6N9GxB42TGuYjLZVHuWVKw6ZFZkNpSjbloumNoTG7uFDS
tbzuTzMyKqtWoNlh06lSRWbkRql7LPvkVfq9DoLxYVw6cdY+C1jH73eDql8+wGM7
y0m+g5f6TPS2V9zr1h96jgf4dKD565rB9TO5cH7OcbdW8fiP2LWk+YreFP+PgitH
FwMeFT74c3k0X/G7WSs2ybYBofneIk43SytRO9vZn17A85yb42Rk4Ffn1bkCuyG4
97hAyaiNmcSfClrDzE9IaWXp1IHiybtC5O5W7fxxjckZ9OOsuFQv/ITCjDiJFwQI
WKK8qu5gTDkpUZ0e7eYRwzTK8uQTzn+uwwAwqW5Nx5SOuNJuXC4oiLxa8KG1IH0U
D81Xwog2yn/xyO3F5cyo6mj6rXTSZ18D2n6Kh3EhHqnPO587GsPh2tN8Kyc01sx4
mmRY6zgv3X3BEBZ4ggaV9UwNOx/0cGIuE1PgXwvtrQa4x34HWM0=
=ouEM
-----END PGP SIGNATURE-----