I agree that hash files should be stored on a separate server, and not on the normal download server (to avoid getting compromised too in case of a hack).
Also I like to point out that Dash also offer both it's binaries and the SHA256SUMS.asc (hash file) on Github .
Link : https://github.com/dashpay/dash/releases (see assets)
I understand there are also ways to verify hash files themselves, by checking who pgp signed them and compare that with developers that have signature rights.
Maybe someone from Dash Core Group can comment on the above ?
I guess we have to wait and see how Monero's official site got compromised in the first place and then check if our own security measurements are still sufficient.
Good to hear that 7zip also has a hash verification tool inside.
Something like this hit another coin I follow. They went after the account without 2fa on github and switched the Windows QT binary, but nothing else. Which is a good reminder for anyone using github make sure to have 2fa setup on top of separate strong passwords on anything important. Dash has some great guides, if they do sign with pgp, is there a guide on how to check the binary against that?