Multi Commander Support Forum

Multi Commander => Feature Requests and Suggestions => Topic started by: ags on December 30, 2024, 15:32:45

Title: [Closed] Support automatic verification for *.sha, *.sha1,*.sha256, *.sha512
Post by: ags on December 30, 2024, 15:32:45

Scenario
- user downloads a file (https://mirror.yandex.ru/mirrors/MX-Linux/MX-ISOs/MX/Snapshots/MX-23.4_December_KDE.iso)
- user also downloads the checksum for the above file (https://mirror.yandex.ru/mirrors/MX-Linux/MX-ISOs/MX/Snapshots/MX-23.4_December_KDE.iso.sha512)

Observed behavior
- MC does not recognize hash file extensions other than *.md5

Requested behavior
- please add other extensions, like *.sha, *.sha1,*.sha256, *.sha512. So the user can check the *.iso by pressing <Enter> on the hash file.

Title: Re: Support automatic verification for *.sha, *.sha1,*.sha256, *.sha512 file extensi
Post by: Jungle on January 01, 2025, 12:03:55

It can be done via MultiScript (at least for some checksum types). The only "problem" is that MC doesn't allow UDC to be used as an action source in File Type setup.

Title: Re: Support automatic verification for *.sha, *.sha1,*.sha256, *.sha512 file extensi
Post by: ags on January 01, 2025, 12:43:55

What I was trying to demonstrate here is this: MC already supports automatic verification of hashes when the user presses <Enter> on an *.md5 file.
This is very convenient for someone who is obligated to use hash verification often. MC offers tools for this (Extension -> File Checksum) but it is a cumbersome implementation and not straigh forward as in other file managers. When you have to do it once is ok, but many times a day it is not. Too many clicks for something that could and should be done by simply pressing <Enter>.

So, to simplify the life of the user, since the functionality already works for md5, it would be nice to work for the other file extensions that contain precalculated hashes.

Title: Re: Support automatic verification for *.sha, *.sha1,*.sha256, *.sha512 file extensi
Post by: Mathias (Author) on January 01, 2025, 13:33:57

Quote from: ags on December 30, 2024, 15:32:45

Scenario
- user downloads a file (https://mirror.yandex.ru/mirrors/MX-Linux/MX-ISOs/MX/Snapshots/MX-23.4_December_KDE.iso)
- user also downloads the checksum for the above file (https://mirror.yandex.ru/mirrors/MX-Linux/MX-ISOs/MX/Snapshots/MX-23.4_December_KDE.iso.sha512)

Observed behavior
- MC does not recognize hash file extensions other than *.md5

Requested behavior
- please add other extensions, like *.sha, *.sha1,*.sha256, *.sha512. So the user can check the *.iso by pressing <Enter> on the hash file.

I will check. can probably be added

This extension is using an old way to connect it self to file extension. It should really be updated to use FileType Setup system instead. but that require lots more rewrites.
So for a first step I might be able to add so it trigger on the *.sha## extensions too.

Title: Re: Support automatic verification for *.sha, *.sha1,*.sha256, *.sha512 file extensi
Post by: ags on January 01, 2025, 14:16:34

Thanks for the reply. Can't wait to test it!  8)

Title: Re: Support automatic verification for *.sha, *.sha1,*.sha256, *.sha512 file extensi
Post by: ags on January 08, 2025, 19:54:19

This functionality was added in 14.6.3056.
Thanks!