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
//! Newtype boundary over RFC 8785 canonical output bytes.
//!
//! [`CanonicalBytes`] makes "these bytes came out of JCS" a type-level
//! fact that digest, signature, and receipt APIs can statically require.
//! Construction is crate-private — the only way to obtain one is to
//! route through [`crate::canonical_bytes_from_slice`] (or the
//! re-export in `vertrule-core::determinism`).
use fmt;
/// Newtype wrapper over canonical JCS output bytes.
///
/// Construction is restricted to this crate — callers obtain a
/// [`CanonicalBytes`] only by routing through
/// [`crate::canonical_bytes_from_slice`] (or the wrappers in
/// `vertrule-core::determinism`). The type exists so digest, signature,
/// and receipt APIs can statically require "bytes that came out of JCS"
/// rather than accepting any `&[u8]`. Every coercion back to `&[u8]`
/// goes through the explicit [`Self::as_slice`] method — there is no
/// `AsRef<[u8]>` or `Deref` impl, so escapes are greppable.
///
/// The `Debug` impl deliberately shows the byte length and not the
/// bytes. Dumping raw canonical JSON into a log is a common way to
/// accidentally leak receipt contents; callers that want the bytes
/// must ask for them.
;