Skip to content
This repository has been archived by the owner on Apr 3, 2019. It is now read-only.

Maybe add cross-check #130

Open
seggen-ibuildings opened this issue Mar 23, 2017 · 4 comments
Open

Maybe add cross-check #130

seggen-ibuildings opened this issue Mar 23, 2017 · 4 comments

Comments

@seggen-ibuildings
Copy link
Contributor

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?

@rjkip
Copy link
Contributor

rjkip commented Mar 23, 2017

Thanks for reporting. I'm inclined to agree, but am not quite sure where we'd host this secondary hash.

@DRvanR
Copy link
Contributor

DRvanR commented Apr 21, 2017

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...

@seggen-ibuildings
Copy link
Contributor Author

Projects that have a website containing an HTML version of the docs always make me happy.

For example, Guzzle has docs inside the repository:

https://github.com/guzzle/guzzle/tree/master/docs

which are also hosted online:

http://docs.guzzlephp.org/en/latest/

@DRvanR
Copy link
Contributor

DRvanR commented Apr 21, 2017

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants