-----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/jalu9uZGunHyUIFAmqg4YUACgkQu9uZGunH
yUJVSQ//bXBrq7vPvxYAGRBYKIjqtiQOvvM8Re/dS9KKy+PKauGK7l5gnMsk5sjc
RrLvwnmfwVn8plDE6NtLyrSZ2MzhddoWPR+hd23yKaTttxUrdsOlYUuHeo54Oq5X
mx3/67uPNHIgwzggyu6KdbB0nrgi2KTBoJo4g1CzMBFX1rLx+EV4RHR9BcwhMYDH
0V2ao/hv78IhB4rRd7xGuEECi5wn11/nvXpsMhmBoR7UqZuNW0VVBG28kh0mj+P+
rTS87Yg+xq1XtTrOkmcRFtO+akttEkSig1Tz74tL+O3luZEWWa/8MiYnfkGVpizE
MVc0/TG/STI7JYuvtw/kFp93HMbN/pQxkl5pDKsep98Iq4k64+gjR21XTa9OwpQT
ElSXiW6/JitWjzFafC8OO1axs8EEgQClfzV1r3N5RCC6FTigluyjWd/olysnV59j
+3Q3mXFIL2UnabihU7HrL1Xfo3mxbDMTgeznQqi06cyYdx2YGDW8/4hR5L4ywxtg
ovZCqFrybghZfQ1Q+AhovQV9o5XBNTqDworsEHAfw2CLyv0Rv1v7kqsq2em/JBVj
QMLyYQKj6QpU4dCRLKDPWUWLvgrmbq4h/vavPTy7VjzVOygsBWZZVh55jL1Drr2r
MXm4vK05qITTtMkjGnu1CQ+Ar58EXmAVfD94L8BzptW9+ZUGWno=
=n15w
-----END PGP SIGNATURE-----