RUT9 Firmware checksum list: Difference between revisions
(→WebUI) |
No edit summary |
||
| Line 13: | Line 13: | ||
==CLI== | ==CLI== | ||
You can calculate the checksum of a firmware image file using '''md5sum'''. When you select a firmware image file for upload via the System -> Firmware page, the file gets uploaded into '''''/tmp/''''' directory with the name '''''firmware.img'''''. So the command to calculate the checksum should look like this: | |||
md5sum /tmp/firmware.img | |||
3839a3ef2b7f483ce0c44304fab7791a /tmp/firmware.img | |||
Bellow the command is the expected response (for RUT9XX_R_00.05.00.5 FW in this example), which contains the checksum and the path to the file. | |||
==WebUI== | ==WebUI== | ||
Revision as of 10:31, 10 September 2018
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 could probably be dangerous and shouldn't be trusted.
To help authenticate Teltonika's RUT9xx router firmware files, we are providing a list of checksums for firmware files that can be download from the RUT9xx Firmware page.
Checksums for RUT9xx firmwares can be calculated with the help of the md5sum application or by checking the checksum displayed in the router's WebUI after uploading a firmware image. The values using both methods are different, so we are providing list of values for both different methods.
CLI
You can calculate the checksum of a firmware image file using md5sum. When you select a firmware image file for upload via the System -> Firmware page, the file gets uploaded into /tmp/ directory with the name firmware.img. So the command to calculate the checksum should look like this:
md5sum /tmp/firmware.img 3839a3ef2b7f483ce0c44304fab7791a /tmp/firmware.img
Bellow the command is the expected response (for RUT9XX_R_00.05.00.5 FW in this example), which contains the checksum and the path to the file.
WebUI
- FW ver.: checksum
- RUT9XX_R_00.03.832: 006cee476568de886e514586d205a7bd
- RUT9XX_R_00.03.850: e44b11bf3a68c6fd35633027d62b806c
- RUT9XX_R_00.03.906: fee184527afd0e2823755d0085d27196
- RUT9XX_R_00.03.923: 5f67eb078ebda98ac597da02ace2e31e
- RUT9XX_R_00.03.946: b3650cd1fccb58f6c20d8b38931193a0
- RUT9XX_R_00.03.965: f433dec03af54cb69167b5c711b1d54a
- RUT9XX_R_00.03.985: 39e38a925b86c6bfcc6e8a17fd692dd7
- RUT9XX_R_00.04.12: ca7ef105a83452e6b02f95c110a74333
- RUT9XX_R_00.04.32: e8f06dbc01b337fe3202e22da1bdf35e
- RUT9XX_R_00.04.38: af3b8b21aebb1916026da77a71e0cfad
- RUT9XX_R_00.04.48: d606f4ed4609995b0acb3b2f3c516fd9
- RUT9XX_R_00.04.57: 40e10bf3a6ed0d0a9dcc8d1da5ff32ed
- RUT9XX_R_00.04.64: b8be480d8fd79abe86343c1733aca5ba
- RUT9XX_R_00.04.75: e5e8049208896c131a66a623301aaeca
- RUT9XX_R_00.04.94: d60d006e30206da025c8a822721f1134
- RUT9XX_R_00.04.103: d8135a5ca19c2c07c024e80d936e7f47
- RUT9XX_R_00.04.112: d674084693dea3bdb63ca6c5fb871e8f
- RUT9XX_R_00.04.125: 7c87631d27a672690c5e0d4e9ac7685a
- RUT9XX_R_00.04.147: 0305e0953bf2260e2ea7454c24b65197
- RUT9XX_R_00.04.153: 728bb528239c33bb3a66cbca018f11aa
- RUT9XX_R_00.04.161: 167ba9b39a650f6e2ea765e5f0bd8514
- RUT9XX_R_00.04.172: 791e5eff448348e15a8ac953dd8afe71
- RUT9XX_R_00.04.199: 2a67dfb0482356f7f9de52b7b82fee2c
- RUT9XX_R_00.04.233: ffd30cdd1b7eede384eaaad7a50dc909
- RUT9XX_R_00.05.00.5: a5fc4c93f8eec213729f45b279dd1f9a
- RUT9XX_R_00.05.01.5: 3c460e566be3bf70048a00fe5a847187