[REQ] Sha-1 support

[ghisler(Author)]

Sounds like a reasonable extension similar to .MD5 files, so I will consider it.

But please dont remove CRC32 and MD5!

Of course not.
To the contrary, I have just added another variant of MD5 files used by freebsd:
MD5 (./subdir/somefile.ext) = e573fe599272957b234dba19e41237a1

[JackFoo]

With so many different formats for the same function how about implementing a template based functionality.

name:normal md5
function:MD5
comment:;
row:[hash][whitespace][file]
-----
name:freeBSD md5
function:MD5
comment:;
row:MD5[whitespace]([file])=[hash]

Seems like a simple thing to implement and will prolly answer all the possible variations.

Cheers.

[Saso]

I am glad you will consider it, since its more and more used. For example, at Fedora Core 4 test distribution they switched entirely from MD5 to SHA-1:

ftp://ftp.belnet.be/pub/mirror/download.fedora.redhat.com/linux/test/3.90/i386/iso/

I also noticed on few occasions 'SHA1SUM' file instead of .sha1 file(s). Maybe you could add support for this SHA1 and MD5. In example, if you click/press enter on SHA1SUM and even MD5SUM, checksum is being verified for given file(s). Format is same as .md5 or .sha1, just file has no extension and SHA1SUM or MD5SUM name. For SFV/CRC32 I didnt see any yet but logically it would be CRC32SUM or SFVSUM.

And besides this I also noticed .sha1sum extension, but its not so common:
https://fxserver.resnet.mtu.edu/isos/Fedora/

So to sum all up, TC could support:
- <name>.sha1 or <name>.sha1sum or SHA1SUM file to verify SHA-1 checksum(s)
- addition of MD5SUM and .md5sum support for verifying MD5 files
- binary mode (indicated by * before file) is default on DOS/Windows - thats already implemented with md5 in new TC


But to keep things simple, created files could use one format, <name>.sha1. For CRC32/SFV I dont know, .sfv is widely used and accepted. Maybe you could add .crc32 extension verify support just for completion.

Nice to hear FreeBDS MD5 format is supported too.