Difference between revisions of "TRB140 Firmware checksum list"
m (Protected "TRB140 Firmware checksum list" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))) |
|||
| Line 9: | Line 9: | ||
Firmware file checksums are listed by firmware release date, from newest to oldest (top to bottom). | Firmware file checksums are listed by firmware release date, from newest to oldest (top to bottom). | ||
| − | ===MD5=== | + | ===Europe, the Middle East, Africa, Korea, Thailand, India=== |
| + | |||
| + | ====MD5==== | ||
---- | ---- | ||
<ul> | <ul> | ||
| Line 19: | Line 21: | ||
</ul> | </ul> | ||
| − | ===SHA256=== | + | ====SHA256==== |
---- | ---- | ||
<ul> | <ul> | ||
| Line 25: | Line 27: | ||
<ul> | <ul> | ||
<li>TRB1400_R_00.01.00: <b>e58068cd4bbcb4edc37d10c18b7ac1112ea76248e5e3c7a57ad6dae94e794a98</b></li> | <li>TRB1400_R_00.01.00: <b>e58068cd4bbcb4edc37d10c18b7ac1112ea76248e5e3c7a57ad6dae94e794a98</b></li> | ||
| + | </ul> | ||
| + | </li> | ||
| + | </ul> | ||
| + | |||
| + | ===South America, Australia, New Zealand, Taiwan=== | ||
| + | |||
| + | ====MD5==== | ||
| + | ---- | ||
| + | <ul> | ||
| + | <li>MD5 checksum: | ||
| + | <ul> | ||
| + | <li>TRB1401_R_00.01.00: <b>75ba44fee48ea7edf84467484b817b29</b></li> | ||
| + | </ul> | ||
| + | </li> | ||
| + | </ul> | ||
| + | |||
| + | ====SHA256==== | ||
| + | ---- | ||
| + | <ul> | ||
| + | <li>SHA256 checksum: | ||
| + | <ul> | ||
| + | <li>TRB1401_R_00.01.00: <b>7911bf611f225fc07f5f84492d65f5e517d3a38569c403b08dab0e7695b57adf</b></li> | ||
</ul> | </ul> | ||
</li> | </li> | ||
</ul> | </ul> | ||
Revision as of 15:57, 4 February 2019
Summary
A checksum is a sequence of hexadecimal symbols generated after running an algorithm called a cryptographic hash function on a file. Calculating a checksum and comparing it with the one provided by the file source can be used as a file authenticity check method.
For example, if you download a file like a firmware image, you should be able to calculate that file's checksum and, if the file is authentic, the checksum should match the one provided by the file's source. If the checksums don't match, it means the file's contents were tampered with, for example, by a malicious third party attacker. This file is probably dangerous and shouldn't be trusted.
Checksum list
Firmware file checksums are listed by firmware release date, from newest to oldest (top to bottom).
Europe, the Middle East, Africa, Korea, Thailand, India
MD5
- MD5 checksum:
- TRB1400_R_00.01.00: 9768dd950babfb2891f5a0e6c0c8f44e
SHA256
- SHA256 checksum:
- TRB1400_R_00.01.00: e58068cd4bbcb4edc37d10c18b7ac1112ea76248e5e3c7a57ad6dae94e794a98
South America, Australia, New Zealand, Taiwan
MD5
- MD5 checksum:
- TRB1401_R_00.01.00: 75ba44fee48ea7edf84467484b817b29
SHA256
- SHA256 checksum:
- TRB1401_R_00.01.00: 7911bf611f225fc07f5f84492d65f5e517d3a38569c403b08dab0e7695b57adf
