Back to matrix

E05-TO: Yes

Rationale

The Guardian documented newsroom SecureDrop operation on 4 April 2024. FPF subsequently identified its SecureDrop service on 18 February 2025, an interval of 320 days. FPF also records the newsroom contributing operational client improvements in late 2024 and June 2025. This supports sustained real-user operation by a news organization independent of the Tor implementation team, rather than a laboratory demonstration or download count. The selected authenticated onion-service role maps to SecureDrop journalist access: its deployment documentation requires the v3 service and persistent app-journalist.auth_private credentials. The public source-submission interface alone is not the authentication witness. The mapping from the operator reports to the documented standard deployment is a documentary inference.

Assessment method

Documentary adoption inference with explicit private-configuration limits; no network or operator audit

Source context

Dated operator report, FPF deployment/release reports and SecureDrop authenticated-v3 onboarding documentation

Outstanding qualification

Credit is for documented sustained Tor/onion-v3 operation with the SecureDrop authenticated journalist workflow. The dated reports establish adoption, not uninterrupted availability or a complete private-configuration audit. No private journalist endpoint was accessed and no credentials were obtained. Exact operator Tor builds, relay logging settings, individual authorization revocation events and optional Conflux deployment are not attested by these sources; no such runtime behavior is certified or newly credited. SecureDrop application login, document encryption and Qubes isolation are not attributed to Tor. Contributions to SecureDrop do not make this newsroom a second independent Tor implementation, and E01 is unchanged. E05 uses the owner-approved adoption rule from revision 6.40. Deployment differences are disclosed rather than imported into the technical column. Independence is assessed from public operator attribution and role, not a private affiliation audit. No runtime, security, uptime or full-profile certification is implied.

Public sources

Editorial evidence references

The following identifiers refer to research records not included in this public package; they are not public links.