1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
//! `refs-core` — a pure-Rust, from-scratch ReFS (Resilient File System) reader.
//!
//! Parses the ReFS on-disk structures a forensic tool needs, starting from the
//! boot Volume Boot Record (VBR) and superblock. Imports as `refs_core` (the
//! bare `refs` crate name is taken by an unrelated third party on crates.io):
//! `use refs_core::BootSector;`.
//!
//! # Reverse-engineered format — no official specification
//!
//! ReFS is **undocumented**: Microsoft publishes no on-disk specification. Every
//! structural fact this reader encodes comes from third-party **reverse
//! engineering** — primarily libyal's `libfsrefs` and Prade's academic work.
//! Correctness is therefore **Tier-2 at best** for structural metadata (there is
//! no ground-truth forensic corpus); only *file content* can reach Tier-1, by
//! hashing against the live Windows ReFS driver. ReFS is also
//! **version-fragmented** — the layout differs materially between v1.x (Server
//! 2012 / 8.1) and v3.x (Server 2016+/Win10+/Win11), and each Windows release
//! tweaks it. This reader targets **v3.x** and **fails loud** (naming the
//! version bytes) on any other major version rather than silently misparsing.
//!
//! # Safety and robustness
//!
//! This crate parses untrusted, attacker-controllable disk images. It is
//! `#![forbid(unsafe_code)]` and every integer is read through bounds-checked
//! little-endian helpers that yield `0`/`None` out of range rather than panic
//! (the Paranoid Gatekeeper standard). ReFS is little-endian.
pub use ;
pub use Checkpoint;
pub use ;
pub use ;
pub use RefsError;
pub use ;
pub use ;
pub use ;