Skip to main contentCrate forensic_mount
Source pub use types::*;
- archive_tree
- Shared synthetic-inode directory tree for archive formats (zip, tar, 7z).
- detect
- filter
- fs_ad1
- AD1 (
AccessData logical image) lazy mount — ad1 feature. - fs_aff4
- AFF4-Logical (
aff4:FileImage) mount — aff4 feature. - fs_apfs
- APFS filesystem support via the
apfs-core crate. Enabled with the apfs
feature flag. - fs_exfat
- exFAT filesystem support via the
exfat-fs crate (MIT). Enabled with the
exfat feature flag. - fs_ext4
- ext4 filesystem support via the ext4fs crate.
Enabled with the
ext4 feature flag. - fs_hfsplus
- HFS+ / HFSX filesystem support via the
hfsplus-forensic crate. Enabled
with the hfsplus feature flag. - fs_iso
- ISO 9660 / Rock Ridge / Joliet filesystem support via the
iso9660-forensic crate. Enabled with the iso feature flag. - fs_ntfs
- NTFS filesystem support via the
ntfs-core crate. Enabled with the ntfs
feature flag. - fs_raw
- fs_sevenz
- 7-Zip (
.7z) archive mount support. Enabled with the sevenz feature flag. - fs_tar
- tar archive mount support — gzip (
.tar.gz/.tgz) or bzip2
(.tar.bz2/.tbz2) compressed. Enabled with the tarball feature flag. - fs_zip
- ZIP archive mount support. Enabled with the
zip feature flag. - fuse_unix
- fusefs
- inode_map
- session
- types
- win_map
- Pure mapping helpers from the platform-agnostic
ForensicFs model onto
Windows filesystem semantics (path components, file attributes, timestamps).
- MountOptions
- Mount options for the FUSE filesystem.
- MountLayout
- How the FUSE mount renders a
ForensicFs.
- ForensicFs
- The core trait that filesystem crates implement.
- build_filesystem
- Construct a
ForensicFs from a seekable byte source and a detected type. - mount
- Mount a forensic filesystem via FUSE (or Dokan on Windows).