/DeployHistory-Recreations

Recreation of gametest1, gametest2, and sitetest1-3's DeployHistories. Gametest3-5 and Sitetest4 will be included as their archive.org snapshots.

DeployHistory Recreations

Recreation of gametest1, gametest2, and sitetest1-3's DeployHistories. Gametest3-5 and Sitetest4 will be included as their archive.org snapshots.

How you can help

This isn't an easy task to do by myself so any help is appreciated.

Getting & Contributing Hashes

TODO: better guide

To get hashes, you can search various anti malware websites. I recommend OTX AlienVault and VirusTotal.

If you find a hash, check it against the DeployHistories here and on the actual sites to make sure you haven't found a duplicate. If it's not a duplicate, wonderful!

To contribute the hash, create an issue with the hash and label it with the appropriate site.

Make sure you have the correct version and date! To get the correct version, right click on the executable of the player or studio (NOT launcher!!) and go to the Details tab. Note what is in the File version row. To get the correct date, go to the Digital Signatures tab, click the signature, and click Details. Copy everything in signing time.

To finally contribute the hash, format your issue with the title as the version hash and the label as the proper site. The body should contain something like this: New [WindowsPlayer|Studio|StudioBeta|Client] [Version Hash] at [Signing date & time formatted as MM/DD/YYYY HH:MM:SS PM|AM], file version: [File Version]...Done!

Example: New WindowsPlayer version-428b22c7474444fe at 2/8/2017 10:31:38 PM, file version: 0, 278, 0, 39156...Done!

Other

commits that include >10 hashes will be formatted as [X]T[#] [date] since these are considered major