Participant Relationship Protocol

Back to matrix

E01-TS: Yes

Rationale

A dated first-hand public report by taavi013 (3 May 2019, BoringTun issue 79) explicitly identifies a working tunnel between an iOS BoringTun client and the Linux kernel WireGuard implementation. The subsequent comment identifies and corrects a Swift-to-C string conversion problem in client construction. Cloudflare documents BoringTun as its independently written Rust implementation, distinct from the original kernel implementation. Tailscale documents its selected data plane as a wireguard-go fork. E01 credits the tested common WireGuard tunnel function, using the same bounded component standard applied elsewhere in the matrix; it does not require whole-stack certification.

Assessment method

Dated public operator test report, independent-code lineage and selected-component mapping

Source context

BoringTun issue 79 and follow-up; Cloudflare implementation announcement; Tailscale WireGuard documentation

Outstanding qualification

Historical operator-reported execution, not an editorial rerun or a current Tailscale-to-BoringTun test. The report gives iOS 12.2, Xcode 10.2 and Rust 1.34.0 but omits exact BoringTun and kernel module revisions, packet captures and a complete reproduction recipe. This limits reproducibility and version coverage rather than negating the explicitly identified cross-implementation exchange. No Tailnet Lock, managed coordination, DERP, mobility, performance or complete-product interoperability is credited. The separate 2026 GotaTun audit remains corroborating execution evidence with an unidentified remote implementation; it is not used to invent that peer identity.

Public sources

Editorial evidence references

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