rars 0.9.3

High-level Rust API for reading, extracting, writing, and repairing RAR archives.
Documentation 
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
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75

//! RAR legacy and modern archive encryption primitives used by `rars`.

pub mod rar13;
pub mod rar15;
pub mod rar20;
pub mod rar30;
pub mod rar50;

/// The longest password any RAR key derivation sees.
///
/// Reference builds copy the password into a 128-element `wchar_t` buffer and
/// keep 127 entries plus a terminator, so nothing past character 127 reaches
/// the KDF. Measured against RAR 7.12: a 133-character password and its first
/// 127 characters open the same archive, and the first 126 do not.
pub const MAX_PASSWORD_CHARS: usize = 127;

/// Cuts a password down to the [`MAX_PASSWORD_CHARS`] the reference tools keep.
///
/// Without this rars derives a key no official tool can reproduce, in both
/// directions: it cannot open a WinRAR archive when handed the same long
/// password, and the archives it writes from character 128 on cannot be opened
/// by WinRAR with that password or with any prefix of it. The boundary is
/// sharp, so a password of exactly 127 characters is untouched.
///
/// A character here is a Unicode scalar, which matches the Linux reference
/// where `wchar_t` is 4 bytes wide. The Windows build has a 2-byte `wchar_t`
/// and so keeps 127 UTF-16 code units instead. The two disagree only for a
/// password carrying astral characters past position 127, where they derive
/// different keys from each other, so no single rule matches both. Scalars win
/// here because truncating UTF-16 can split a surrogate pair, and a Rust `str`
/// cannot hold the lone surrogate that would produce.
pub fn clamp_password(password: &[u8]) -> &[u8] {
    match std::str::from_utf8(password) {
        Ok(text) => match text.char_indices().nth(MAX_PASSWORD_CHARS) {
            Some((byte_offset, _)) => &password[..byte_offset],
            None => password,
        },
        // RAR 1.3 through 2.0 take single-byte OEM/ANSI passwords, so one byte
        // is one character.
        Err(_) => &password[..password.len().min(MAX_PASSWORD_CHARS)],
    }
}

#[cfg(test)]
mod tests {
    use super::{clamp_password, MAX_PASSWORD_CHARS};

    #[test]
    fn clamp_password_keeps_127_characters() {
        let short = b"hunter2";
        assert_eq!(clamp_password(short), short);

        let exact = "A".repeat(MAX_PASSWORD_CHARS);
        assert_eq!(clamp_password(exact.as_bytes()), exact.as_bytes());

        let long = "A".repeat(130) + "ZZZ";
        assert_eq!(clamp_password(long.as_bytes()), exact.as_bytes());
    }

    #[test]
    fn clamp_password_counts_characters_not_bytes() {
        // 140 astral scalars: 560 UTF-8 bytes, 280 UTF-16 code units.
        let emoji = "\u{1F600}".repeat(140);
        let clamped = clamp_password(emoji.as_bytes());
        let text = std::str::from_utf8(clamped).unwrap();
        assert_eq!(text.chars().count(), MAX_PASSWORD_CHARS);
        assert_eq!(clamped.len(), MAX_PASSWORD_CHARS * 4);
    }

    #[test]
    fn clamp_password_falls_back_to_bytes_when_not_utf8() {
        let latin1 = vec![0xe9u8; 200];
        assert_eq!(clamp_password(&latin1).len(), MAX_PASSWORD_CHARS);
    }
}