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

md5:
d71db59e76e908f2810b6dcf9b742ca1
sha1:
3713c76a9a230d30d2d28ccc0e1c164eb73916ca
sha256:
363f5edef02500bb9faf5a557bb5b77c463e3b7f11fcee283ff4d0614d1e88d8
sha512:
9b2ced771ecae2175569d0a6cfd02278ddd1d1d2398e48a5d9de31b7a66cbaf831ed8652cc101a1cff46a9176ffe9b835fc728fe1484a1e7c853ca2c4d9d813d

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/jalu9uZGunHyUIFAmqZ/5wACgkQu9uZGunH
yUJIkA//YZ1F3PTd9AVXS/bVN6/7rv9uV71LSGcREU358wo+0dZ/puB/j4xGZrrG
7UEHKkBXKhEIyYBDzqbn8xa9D+4S4ubd9x2aMvOe++GxkixVKQSAdYC3OFwgNH+V
CLFGAnbuTd3wqXhrUFk/6XA+R8rCzLSbvifBl72t8sUpcVI0D52FaZfLyg/ow/S8
R+IshEzqDshTHddMKda78ZzMmWIb+wqJgOyK8aHfqkvHTYgTSP6gqsYkwxkgYTMd
G2kXi8pfkgZcBqBsEwCSQpXeU3WPd99fVmYpnXEjIR6jj5qmqJZ0+BxK3ISLGFBz
5Xi1tJi2dyJJXGa+fz+s+EIH44bALlppLxcuBLY4CeJsj1AO9fg8P5iOCN9lrkq5
QP2hYsDSGkJMYYDns+uqUrgo1W8ea8vRctg3yg04eHSHS+J9BxLw3xyRxo1nC0tr
VyXmWH2NNMEwQnwj5nYdgk8///P4sVoKqaqg4HMPRRxTzWDXojnxZQeYMNZi9dCx
gpYy520QDgDiJd3zEbiEDUMNXGu1ZFFV40NV98Gs/Yx7d3aNJ0J+mGkyhyD5ePRz
0S4LtQCI8UugltbdkSkCRMz4sMILoEcaPL4kk2zhUj1EGu8Q3Y9huf/5RdsJkJs1
7O6IHmRQWbFHZbBRu+EnbxpjYJI2Av3uoAUWscaYiQcpiJl0vsI=
=1CPN
-----END PGP SIGNATURE-----