Without being able to skip the hash check, I have to do it for every tracker.Ĥ. Cross-seeding (seeding the same torrent on several trackers using different metafiles) is quite common among private trackers. So even if I created the torrent myself, I still have to check the hash after adding the torrent with the changed hash.ģ. Private trackers usually change the hash when uploading a torrent. I don't use Deluge to create really big torrents since the build-in torrent creater doesn't allow pieces of 16 MiB. Skipping hash checks come handy in the following three scenarios:ġ. I'd like to explain why I need it and why (I think) it's actually not a bad idea. I'd like a skip hash check option when adding a new torrent. The two native tools get-filehash and certutil are quite handy for the quick computation of hashes on Windows, and also for script use.I know this has been requested before, but it was declined and the last thread got totally off topic. You may use the commands in scripts to compute hashes for several files in one operation. certutil -hashfile c:\example.txt SHA512. To use a different hash algorithm, specify it after the command, e.g. You may specify the hash algorithm as well.
The base command is certutil -hashfile PATH, e.g. You can run the program from the command prompt, or using PowerShell. CertUtilĬertUtil is another native Windows program that you may use to compute hashes of files. The core difference between path and literalpath is that literalpath supports no wildcards, and is used exactly as it is typed.
You may also use -LiteralPath or -InputStream instead of the default path option.
So, to generate a Sha512 hash you would use the command get-filehash -Algorithm Sha512 c:\test.txt.
0 kommentar(er)
