Repository navigation
Add a file_digest() function in hashlib #89313
Description
Activity
I am proposing the addition of a very simple helper to return the hash of a file.
- addedstdlibStandard Library Python modules in the Lib/ directoryStandard Library Python modules in the Lib/ directory
on Sep 9, 2021 - addedstdlibStandard Library Python modules in the Lib/ directoryStandard Library Python modules in the Lib/ directory
on Sep 9, 2021 - added3.11only security fixesonly security fixestype-featureA feature request or enhancementA feature request or enhancement
on Sep 9, 2021 Hey Tarek, long time no see!
-
the _sha256 module is optional, can be disabled and is not available in some distributions.
-
I also don't like to use sha256 has default. It's slow, even slower than sha512. Any default makes it also harder to upgrade to a better, more secure default in the future.
-
like hmac.new() a file_digest() should accept PEP-452-compatible arguments and hash name as digstmod argument, not just a callable.
-
a filename argument prevents users from passing in file-like objects like BytesIO.
-
4096 bytes chunk size is very conservative. The call overhead for read() and update() may dominate the performance of the function.
-
The hex argument feels weird.
In a perfect world, the hash and hmac objects should get an "update_file" method. The OpenSSL-based hashes could even release the GIL and utilize OpenSSL's BIO layer to avoid any Python overhead.
-
Hey Christian, I hope things are well for you!
Thanks for all the precious feedback, I'll rework the patch accordinglyTarek,
Are you still working on this? Would you like me to take over?
Aur
@aur, go for it, I started to implement it and got lost into the details for each backend..
OK, I'll give it a go.
PR contains a draft implementation, would appreciate some review before I implement the same interface on all builtin hashes as well as OpenSSL hashes.
5 remaining items
I don't think HMAC of a file is a common enough use case to support, but I have absolutely no problem conceding this point, the cost of supporting it is very low.
I/O in C is a world of pain in general. In the specific case of
io.RawIOBaseobjects (non-buffered binary files) to my understanding it's not that terrible (am I right? Does my I/O code work as-is?). To my understanding, providing a fast path just for this case that calculates the hash without taking the GIL for every chunk would be very nice to have for many use cases.Now, we could just be happy with
file_digest()having anifforisinstance(io.RawIOBase)that chooses a fast code path silently. But since non-buffered binary files are so hard to tell apart from other types of file-like objects, as a user of this code I would like to have a way to say "I want the fast path, please raise if I accidentally passed the wrong things and got the regular path". We could havefile_digest('sha256', open(path, 'rb', buffered=0), ensure_fast_io=True), but I think for this use caseraw_file_digest('sha256', open(path, 'rb', buffered=0))is cleaner.In all other cases you just call
file_digest(), probably get the Python I/O and not the C I/O, and are still happy to have that loop written for you by someone who knows what they're doing.For the same reason I think the fast path should only support hash names and not constructors/functions/etc', which would complicate it because new-object-can-be-accessed-without-GIL wouldn't necessarily apply.
Does this make sense?
@tiran Can you made a PR adding the
file_digestto the 3.11 what's new, please?- added a commit that references this issue
on Aug 13, 2022 Hey folks.
I know this is closed and perhaps I should simply file a new request... but would you consider to extend the interface of that function to (efficiently) calculate a file's hashsum for multiple algorithms (i.e. without reading it once for every algo)?
One could perhaps do so by accepting some array for
digestand return a dict where the alogo name is the key and the hashvalue the value.
Or perhaps something smarter ^^Cheers,
Chris.Please file a new feature request issue here for that.
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields: