-----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/jalu9uZGunHyUIFAmrG6YcACgkQu9uZGunH
yUJrVg/9FNF0FgXBUBTrX+0CAfQYuhZ4LWaQ/YtlCdPoL/VJOP1S8E/wlRrR5W92
0CKGMfS/8mXmDRRVWHoR23NXhCRR5MtxRsc7VR4SQ+gH7/X8WLXCxxNwqySMsW1t
503BPtfRyyWRtkKpugdl28V7I2z/Zl1VLSUmHZC0wlGwOCD4yBKDEgh7H2i7QX+e
tBLgexAislW5QDrcBAd1Tf23sJPwhg2L8/Eqk84HCRP+wd8utmaibV70WTRe47uO
GGHXL923v77d+zI4vzI+/JlLVYZeNPYsh82yJmvTC6giLyhMXknrIk/Ulpn0MXKB
0DqnsHGLKibZuE5TltFGkuBPdztc+vLR056N8n0oj1snl0pKmT7oaf5N8mqSuhkm
f1oiDzWqZgBUBjd4iRz1/INRdgnzhJGqCx/EvNmGNuAsrgX2w/kAoukiulH5i91l
BH9vyLKZDlZGKrHf/eIbQOVIB2823pPKOZY/LLnTC3H8DhztxS+C7Bj9HCABeKRF
eHtgbWx5kF3MKJ7Nw6/KfbF9E/wd+8c/w4sO+KD3Jp9axVLNKMZOmpUyH+Spt+ZK
IfG8NMvMgi2ioZuuwZ6sZCW0uGV7DkFZDb4wluEbJ27nfONPJDdc98DZ7SezTjzn
1E+sKulytXRasOJ4N5ldWKEIWF7rhNvqAc4KZD7Rc4epnoM48ac=
=7BWk
-----END PGP SIGNATURE-----