[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[tor-dev] Re: entrymap: A fast, modular scanner for Entry Guards & HSDirs (Complementing exitmap)
Hi tor-dev team, Tor Network Health Team & Developers
Following up on our initial proposal, we wanted to share a brief update on three additional analysis modules we completed for entrymap today, along with an automated 1:1 Tor Directory
Specification (dir-spec.txt) verification hook that executes after every scan run.
==============================================================================
1. CONTEXT: HYGIENE & PROTOCOL DRIFT VS. MALICE
==============================================================================
When analyzing ingress telemetry across the consensus, it is crucial to emphasize that many observed anomalies are likely benign artifacts of operator convenience or configuration
friction, rather than malicious intent:
• Managing MyFamily across dozens of dynamic instances is notoriously cumbersome for well-meaning operators.
• Setting BandwidthRate to high or default maximum limits is often an operator's way of saying "use all available bandwidth," leaving it to Bandwidth Authorities to measure true
capacity.
However, from an architectural perspective, these configuration patterns still create structural imbalances in circuit diversity and consensus weights. entrymap was built to give the
Network Health team clear, automated visibility into these edge cases.
==============================================================================
2. NEW MODULES ADDED TODAY
==============================================================================
1. ghost_bw (Bandwidth Disparity & Integer Limit Auditing)
• Inspects disparities between claimed BandwidthRate in descriptors and real observed throughput.
• Automatically identifies configurations setting rates to 32-bit integer boundaries (e.g. 2^30 B/s / 1 GiB/s) which, during descriptor churn or measurement delays, can skew
consensus weight calculations before authorities re-balance them.
2. cidr_cluster (CIDR Subnet Diversity Auditing)
• Evaluates /24 IPv4 subnet concentration among Guard and HSDir relays.
• Audits instances where multiple relays reside in the exact same /24 subnet without mutual family declarations, surfacing potential gaps where Tor clients might select path hops
within the same IP block despite the /16 diversity heuristic.
3. bulletproof (Offshore Ingress Hubs & Exit Policy Auditing)
• Audits ingress relays deployed in non-cooperative offshore or privacy-centric hosting jurisdictions that enforce strict "reject *:*" exit policies (operating purely as
ingress/directory funnels with zero exit capability).
==============================================================================
3. AUTOMATED 1:1 SPECIFICATION VERIFICATION HOOK (dir-spec.txt)
==============================================================================
To ensure entrymap maintains zero false positives and adheres strictly to official protocol standards, we implemented an automated post-execution verifier (run_spec_verification):
• Verifies mathematical calculations (disparity ratios, bandwidth rates) against dir-spec §2.1.1.
• Evaluates family non-repudiation assertions against dir-spec §5.2 to distinguish true undeclared nodes from parser singletons.
• Executes automatically at the conclusion of every module run to audit descriptor integrity against raw directory consensus.
Verification Hook Output:
----------------------------------------------------------------------
🔬 1:1 SPECIFICATION VERIFIER: Module audit complete.
• Mathematical & Descriptor Assertions Checked: Conforming
• Specification Drift / Inconsistencies Detected : 0
• Protocol Integrity Status: ✅ 100% VERIFIED TO DIR-SPEC
----------------------------------------------------------------------
==============================================================================
4. CONCLUSION
==============================================================================
Our goal is simply to offer the Tor community an automated, modular tool for the ingress boundary that operates with the same rigor and reliability as exitmap does for the egress
boundary.
We welcome feedback, suggestions for additional heuristics, or collaboration on gitlab.torproject.org/tpo/network-health.
Best regards,
Adam Keeves
FrogSec Research
keevesadam98@xxxxxxxxx
_______________________________________________
tor-dev mailing list -- tor-dev@xxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to tor-dev-leave@xxxxxxxxxxxxxxxxxxxx