Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: When verifying a hash file, only calculate the algorithm in the file. #55

Closed
tERyceNzAchE opened this issue Jan 31, 2021 · 4 comments
Labels
enhancement New feature or request

Comments

@tERyceNzAchE
Copy link

When verifying a hash file, to increase performance only calculate and show the algorithms used in the hash file.

@namazso
Copy link
Owner

namazso commented Jan 31, 2021

This is possible already in 3.0.1 (pre-release currently) but not really communicated well. Simply unselect all algorithms. The correct one (if detected from extension) is always automatically enabled. I'll think of making this explicitly an option

@tERyceNzAchE
Copy link
Author

Perhaps I wasn't clear. User should not have to unselect all algorithms, OpenHashTab should do that automatically if it is in verify mode.

Having multiple algorithms enabled when not in verify mode is very useful.

@namazso
Copy link
Owner

namazso commented Jan 31, 2021

I see. I'll probably add this as an option soon. Also, just a sidenote: it isn't too bad performance-wise to calculate all of them - usually the bottleneck is (if not the disk) the slowest algorithm. So if you calculate some SHA-2 hash, you get SHA-1 and MD5 for practically free.

@namazso namazso added the enhancement New feature or request label Jan 31, 2021
@tERyceNzAchE
Copy link
Author

Thanks.

I'm using 3.0.1 now and it can be pretty bad when I'm verifying a large directory (10+ GB) and have several algorithms enabled. Not horrible, but very noticeable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants