Mirrored_Repos/awesome-lego-universe
1
0
Fork 0
mirror of https://github.com/EliteMasterEric/awesome-lego-universe.git synced 2025-10-31 04:31:56 +00:00
Code Issues Packages Projects Releases Wiki Activity

Completed checksum guide.

Browse Source
This commit is contained in:
Eric Myllyoja
2021-12-06 08:56:41 -05:00
parent 88665052a1
commit ad29338dc6
1 changed files with 34 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

39
verify-my-client.md
View File

@@ -24,22 +24,51 @@ Add on top of that the odds that the file isn't a garbled mess, on top of the od
I'll go over a tutorial for each computer in a moment, but simply put, you'll be performing the following steps:
* Start with the file containing the client (it should be a single .rar file)
* Start with the file containing the client (it should be a single .rar file).
* Run the checksum function on the file to generate a checksum string.
* Compare it with the known good checksums available below.
If the checksum string you generated matches one of the ones below, it is guaranteed to be safe.
### Valid Checksums
Here is a list of known valid
Here is a list of known valid checksums for up-to-date LEGO Universe Clients.
- `8f6c7e84eca3bab93232132a88c4ae6f8367227d7eafeaa0ef9c40e86c14edf5` (packed client, rar compressed)
- `c1531bf9401426042e8bab2de04ba1b723042dc01d9907c2635033d417de9e05` (packed client, includes extra locales, rar compressed)
- `0d862f71eedcadc4494c4358261669721b40b2131101cbd6ef476c5a6ec6775b` (unpacked client, includes extra locales, rar compressed)
## Windows
With how useful taking the checksum of a file is, it's really something that Windows should make easier to do. Just add it to the Properties panel or something!
### WORK IN PROGRESS
1. Open a command line terminal (cmd.exe).
2. Run the following command, replacing `<file>` with the path to your client.
```
certutil -hashfile <file> SHA256
```
3. The command will output a long string of characters.
- Compare it to make sure it matches one of the ones above.
- If your client is out-of-date, corrupted, or potentially malicious, the SHA256 checksum will significantly differ from the ones above.
## MacOS
### WORK IN PROGRESS
1. Open a command line terminal.
2. Run the following command, replacing `<file>` with the path to your client.
```
shasum -a 256 <file>
```
3. The command will output a long string of characters.
- Compare it to make sure it matches one of the ones above.
- If your client is out-of-date, corrupted, or potentially malicious, the SHA256 checksum will significantly differ from the ones above.
## Linux
### WORK IN PROGRESS
1. Open a command line terminal.
2. Run the following command, replacing `<file>` with the path to your client.
```
shasum -a 256 <file>
```
3. The command will output a long string of characters.
- Compare it to make sure it matches one of the ones above.
- If your client is out-of-date, corrupted, or potentially malicious, the SHA256 checksum will significantly differ from the ones above.