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
//! The DNS provides a single, global, hierarchical namespace with (when DNSSEC is used)
//! cryptographic guarantees on all of its data.
//!
//! This makes it incredibly powerful for resolving human-readable names into arbitrary, secured
//! data.
//!
//! Unlike TLS, this cryptographic security provides transferable proofs which can convince an
//! offline device, using simple cryptographic primitives and a single root trusted key, of the
//! validity of DNS data.
//!
//! This crate implements the creation and validation of such proofs, using the format from RFC
//! 9102 to create transferable proofs of DNS entries.
//!
//! It is no-std (but requires `alloc`) and seeks to have minimal dependencies and a reasonably
//! conservative MSRV policy, allowing it to be used in as many places as possible.
//!
//! Most of the crate's logic is feature-gated, and *all dependencies are optional*:
//! * By default, the `validation` feature is set, allowing to validate DNSSEC signatures and
//! proofs using the [`validation`] module.
//! * The `std` feature enables the [`query`] module, allowing for the building of proofs by
//! querying a recursive resolver over TCP.
//! * The `tokio` feature further enables async versions of the [`query`] methods, doing the same
//! querying async using `tokio`'s TCP streams.
//! * Finally, the crate can be built as a binary using the `build_server` feature, responding to
//! queries over HTTP GET calls to `/dnssecproof?d=domain.name.&t=RecordType` with DNSSEC
//! proofs.
//!
//! The `slower_smaller_binary` feature slows proof validation down by 50%+ for a very marginal
//! reduction in binary size, but those who are extremely binary size constrained may still find it
//! useful.
// why is this even a lint
// Why in the hell is this a lint?
// Sometimes this improves readability
// lifetimes improve readability
// borrows indicate read-only/non-move
// sometimes we don't have an option
// sometimes identities improve readability for repeated actions
// sometimes identities improve readability for repeated actions
extern crate alloc;
/// The maximum number of requests we will make when building a proof or the maximum number of
/// [`rr::RRSig`] sets we'll validate records from when validating proofs.
// Note that this is duplicated exactly in src/http.rs
pub const MAX_PROOF_STEPS: usize = 20;
pub