#data #filesystem #digest #hash


Library implementing recursive digest for filesystem directories

7 releases (4 breaking)

0.5.0 Jul 31, 2021
0.4.0 Mar 8, 2020
0.3.0 Mar 8, 2020
0.2.1 Dec 28, 2018
0.1.1 Dec 19, 2018

#56 in Filesystem

Download history 2240/week @ 2021-08-08 956/week @ 2021-08-15 1097/week @ 2021-08-22 881/week @ 2021-08-29 983/week @ 2021-09-05 105/week @ 2021-09-12 82/week @ 2021-09-19 69/week @ 2021-09-26 64/week @ 2021-10-03 73/week @ 2021-10-10 121/week @ 2021-10-17 156/week @ 2021-10-24 111/week @ 2021-10-31 104/week @ 2021-11-07 137/week @ 2021-11-14 93/week @ 2021-11-21

1,122 downloads per month
Used in 6 crates (4 directly)

MPL-2.0 OR MIT OR Apache-2.0

303 lines

Recursive file-system digest

This library implements a simple but efficient recursive file-system digest algorithm. You have a directory with some content in it, and you'd like a cryptographical digest (hash) of its content.

It was created for the purpose of checksuming source code packages in crev, but it is generic and can be used for any other purpose.


Given any digest algorithm H (a Hash function algorithm), a RecursiveDigest(H, path) is:

  • for a file: H("F" || file_content)
  • for a symlink: H("L" || symlink_content)
  • for a directory: H("D" || directory_content)

As you can see a one-letter ASCII prefix is used to make it impossible to create a file that has the same digest as a directory, etc. The drawback of this approach is that RecursiveDigest(H, path) of a simple file is not the same as just a normal digest of it (H(file_content)) .

file_content is just the byte content of a file.

symlink_content is just the path the symlink is pointing to, as bytes.

directory_content is created by:

  • sorting all entries of a directory by name, in ascending order, using a simple byte-sequence comparison
  • for all entries concatenating pairs of:
    • H(entry_name)
    • RecursiveDigest(H, entry_path)

If optional additional data extensions is used, the H(entry_name) above becomes H(entry_name || 0 || additional data). The format and meaning of additional data is unspecified, but was intendet for fielsystem metadata like file system permissions and ownership.


~28K SLoC