FINDING · POLICY
The paper proposes an Internet Freedom vulnerability registry with five design principles: persistent cross-vendor tracking under shared identifiers (e.g., IF-ARCH-2025-001) as long as a risk remains reproducible; human-centered impact ratings anchored to harm potential for journalists and dissidents rather than CVSS-style exploitability scores; timestamped re-verification hooks with linked PCAPs and minimal reproduction scripts; a structured media interface to counter vendor narrative capture; and open public APIs for integration into risk dashboards so that users of tools like Orbot or Lantern can directly query their configuration's exposure to known metadata-based attacks.
From 2026-tolley-architectural — Architectural VPN Vulnerabilities, Disclosure Fatigue, and Structural Failures · §6.1–6.5 · 2026 · Free and Open Communications on the Internet
Implications
- Circumvention tool projects should publish adversary-aligned re-testing results (not just changelogs or CVE references) in a machine-readable format compatible with persistent architectural vulnerability tracking.
- Digital safety trainers and tool vetting programs should require vendors to disclose architectural limitations alongside CVE status, and treat 'no active CVE' as insufficient evidence of safety for high-risk users.
Tags
Extracted by claude-sonnet-4-6 — review before relying.