You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 3, 2019. It is now read-only.
The SHA-384 checksum is good for security, of course. But it isn't of much use if the GitHub account is hacked, since both the file and the hash are on GitHub.
The composer installer is on getcomposer.com, but it has a cross-check on GitHub, so that you can verify the checksum yourself.
Shouldn't we have a cross-check as well?
The text was updated successfully, but these errors were encountered:
the secondary hash could perhaps be hosted on one of the IB servers? Or on a publicly readable file on google drive? Or we could simply create a quick website for the qa-tools and host it there...
The SHA-384 checksum is good for security, of course. But it isn't of much use if the GitHub account is hacked, since both the file and the hash are on GitHub.
The composer installer is on getcomposer.com, but it has a cross-check on GitHub, so that you can verify the checksum yourself.
Shouldn't we have a cross-check as well?
The text was updated successfully, but these errors were encountered: