RUT2 Firmware checksum list: Difference between revisions
No edit summary |
(→CLI) |
||
Line 16: | Line 16: | ||
9ac06b19353b7c61753a9f572d21a92e /tmp/firmware.img | 9ac06b19353b7c61753a9f572d21a92e /tmp/firmware.img | ||
Bellow the command is the expected response (for | Bellow the command is the expected response (for RUT2XX_R_00.01.02.3 FW in this example), which contains the checksum and the path to the file. If the checksum of the firmware file you downloaded doesn't match with the one provided here, your file must have been tampered with and '''you shouldn't proceed with the firmware update'''. | ||
Checksums for RUT2xx firmwares (CLI) are as follows: | Checksums for RUT2xx firmwares (CLI) are as follows: |
Revision as of 16:33, 11 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 is probably dangerous and shouldn't be trusted.
To help authenticate Teltonika's RUT2xx router firmware files, we are providing a list of checksums for firmware files that can be download from the RUT2xx Firmware page.
Checksums for RUT2xx 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 9ac06b19353b7c61753a9f572d21a92e /tmp/firmware.img
Bellow the command is the expected response (for RUT2XX_R_00.01.02.3 FW in this example), which contains the checksum and the path to the file. If the checksum of the firmware file you downloaded doesn't match with the one provided here, your file must have been tampered with and you shouldn't proceed with the firmware update.
Checksums for RUT2xx firmwares (CLI) are as follows:
- FW ver.: checksum
- RUT2XX_R_00.01.03.2: 687a474f0b06f90ab7e2e70ef98b58ac
- RUT2XX_R_00.01.02.6: 6a141d1caab0874c9b63d9ce28cc94d0
- RUT2XX_R_00.01.02.3: 9ac06b19353b7c61753a9f572d21a92e
- RUT2XX_R_00.01.01.4: 78ee432012897da8b2215d0e3c6abc42
- RUT2XX_R_00.01.01.00: 87a6506e2962c8fee5db599b104db98f
- RUT2XX_R_00.00.553: 2483425fb1c2c4509680dfe0dd2cc5ef
- RUT2XX_R_00.00.539: 3ec22055e89d4a05cba8557cc1615eec
- RUT2XX_R_00.00.486: ce69ee7f04c5776b5ff0ec5e4724f263
- RUT2XX_R_00.00.482: 1b30c3ea977e7ddec3409fc6e6ee03a8
- RUT2XX_R_00.00.474: 660ac126a8911e20f3b5b85b89ec7d4b
- RUT2XX_R_00.00.388: 106aa753ba18bca6df825d581691217a
- RUT2XX_R_00.00.382: 825997630af0399bb6dae182c7d9fe4b
- RUT2XX_R_00.00.377: 3487e2cca8205de4e951a1c5e72bf3ca
- RUT2XX_R_00.00.372: 15d241761873db6cf4b03f36690b15e6
- RUT2XX_R_00.00.355: 44954ab35e562e6eca39401ce5df3bdc
- RUT2XX_R_00.00.339: 13da9492bdad38b2e50d7aebe06157d9
- RUT2XX_R_00.00.312: 42b64d5fbd5f15bbddfaceb6d3d23487
- RUT2XX_R_00.00.307: e4ecd14654fccbc0f2955c21b0752096
- RUT2XX_R_00.00.296: 76d0ceeacd8cac3e5ecaa6e2aac75aa3
- RUT2XX_R_00.00.284: e64b798e5053ddb7a07c663753db6623
WebUI
You can also check the checksum of a firmware file via the router's WebUI. When you upload a firmware image file and click upgrade, the firmware is uploaded and you are redirected to another window, where you have to confirm the upgrade. In this window, the checksum is displayed as well, but it is different than the one you get from CLI.
Checksums for RUT2xx firmwares (WebUI) are as follows:
- FW ver.: checksum
- RUT2XX_R_00.01.03.2: f05ae68ebc30d0497062b67d2ad3f94c
- RUT2XX_R_00.01.02.6: dcb3ed6a48e4c27748c9c7795e6dcd15
- RUT2XX_R_00.01.02.3: 22d2510df6a3f2cb7443f0521c25e367
- RUT2XX_R_00.01.01.4: dd6defed845c3b1241826bffde38f08a
- RUT2XX_R_00.01.01.00: 110dc5fab62cabdf67877f26fa8fa924
- RUT2XX_R_00.00.553: c1359554ab6c8bb5e775c24ef693b280
- RUT2XX_R_00.00.539: ae4c13c275fedd8bb5180c610a8f387a
- RUT2XX_R_00.00.486: e225813d9baac399434f980058111df9
- RUT2XX_R_00.00.482: b8ac4078ee364851d39e430739c00711
- RUT2XX_R_00.00.474: 17cd9dbe8ff4190fb54a7d1e8a5f22a2
- RUT2XX_R_00.00.388: f89224948117c22707595f326e4b9c38
- RUT2XX_R_00.00.382: b7cc349570e99d141597489c61064931
- RUT2XX_R_00.00.377: 713df01f8fc19a15c100dd07f868ec8e
- RUT2XX_R_00.00.372: 84fa0a0a8d5b1d7f758e0da2c7bdf2c2
- RUT2XX_R_00.00.355: 09ace4b06718c3bd722d7785e4c80606
- RUT2XX_R_00.00.339: 46e9f561e5f5a456ee71c12c483e73c7
- RUT2XX_R_00.00.312: 057fa357bf0c4b2a90b3098e8aabc078
- RUT2XX_R_00.00.307: c38101f401f5c1eb50321d10edd77b4c
- RUT2XX_R_00.00.296: bfa44fad547039c836ea5e2bdd031a71
- RUT2XX_R_00.00.284: b37599e6778dc7e28a14d73ab7fc89b4