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
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
// Copyright (c) 2026 Erik Lening (hollowpointer) and Contributors
//
// This file is part of Zond Engine, licensed under the GNU Affero General
// Public License, version 3 or later. See the LICENSE file for details, or
// <https://www.gnu.org/licenses/agpl-3.0.html>.
//
// SPDX-License-Identifier: AGPL-3.0-or-later
//! # Why a port is in the state it is
//!
//! [`PortState`](super::PortState) is the verdict; [`Discovery`] is the
//! evidence behind it: which packet decided it, when, how long it took to
//! arrive, and which of this host's interfaces it arrived on.
//!
//! Kept beside the verdict rather than folded into it because the two are read
//! by different people for different reasons. A report renders the verdict; an
//! operator who does not believe the verdict reads this. A TTL of 64 against a
//! host three hops away, or a `Closed` sourced from an address that is not the
//! target's, is how a wrong answer is caught, and none of it is recoverable
//! once the state has been recorded on its own.
//!
//! Everything except the reason is optional, because an unprivileged connect
//! attempt knows only that it succeeded or failed: there is no header to read a
//! TTL from and no interface it can name.
use ;
/// The packet that settled a port's state, named rather than interpreted.
///
/// What any of these *means* depends on the probe that provoked it, which is
/// [`TcpScanTechnique::verdict`](crate::model::technique::TcpScanTechnique::verdict)'s
/// job. Recording the segment rather than the conclusion is what lets a reader
/// disagree with the conclusion.
///
/// `#[non_exhaustive]`: a scan learns to recognise new replies as it learns to
/// send new probes, and a consumer matching on this should pay for that with a
/// recompile rather than with a major version.
/// The evidence behind a port's state: which packet decided it, when, how long
/// it took, and where it came from.
///
/// The two times answer different questions and neither substitutes for the
/// other. `timestamp` places the finding on a timeline a person reads, so it is
/// wall-clock. `rtt` is measured elapsed time, and stays correct across a clock
/// adjustment mid-scan because it was never derived from the clock.
// ╔════════════════════════════════════════════╗
// ║ ████████╗███████╗███████╗████████╗███████╗ ║
// ║ ╚══██╔══╝██╔════╝██╔════╝╚══██╔══╝██╔════╝ ║
// ║ ██║ █████╗ ███████╗ ██║ ███████╗ ║
// ║ ██║ ██╔══╝ ╚════██║ ██║ ╚════██║ ║
// ║ ██║ ███████╗███████║ ██║ ███████║ ║
// ║ ╚═╝ ╚══════╝╚══════╝ ╚═╝ ╚══════╝ ║
// ╚════════════════════════════════════════════╝