Skip to main content

Module pairing

Module pairing 

Source
Expand description

§Deciding which record describes which host

Ports pair by number and transport, which is exact. Hosts do not: a machine can change address between two scans, answer at one address in one scan and another in the next, or be seen as one record by a privileged scan and two by an unprivileged one. Pairing them wrong invents a host that appeared and one that vanished.

§How the decision is made

Each record yields a set of identity tokens under the caller’s HostIdentity policy. A baseline record and a current record are linked when they share a token. The links form a bipartite graph, and each connected component of that graph is one host as far as the comparison is concerned.

Greedy pairing would have to break ties, and a tie is information. A component with one record on each side is the ordinary case. One record on one side and two on the other means the scans grouped the same addresses differently, which is reported as such.

fe80::1 names a different machine on every segment, so the token for a link-local address includes the zone the record was found on.

A record that names no zone gets no zone in its token, and two of those at one address fold together. Only a scan that reached the link layer records a zone, so a report rebuilt from a foreign scanner’s output always lands here. Pairing under PrimaryAddress declines the guess.

Enums§

HostIdentity
What makes two records, in two different scans, the same host.