this post was submitted on 28 Jun 2026
14 points (100.0% liked)

netsec

1463 readers
1 users here now

Technical news and discussion of information security.

Rules:

  1. Be excellent to each other
  2. Keep it on topic
  3. Absolutely no PII or doxing
  4. No disclosure posts

founded 3 years ago
MODERATORS
 

I made a discovery while digging into GSM signaling architecture. When you forward a call cross-carrier, each carrier in the chain only sees adjacent hops. That's just how GSM works. But that means cross-carrier forwarding behaves like a proxy chain. This is a fundamental property of the protocol, not something engineered on top of it. That realization is what CAMO is built on. If cross-carrier forwarding produces partial visibility at each node by default, you can compose that property deliberately. Add M2M private APNs for jurisdictional breaks, rotating eSIM pools so no stable SIM identity persists, WireGuard tunnels between nodes, a signed gossip protocol for node discovery and what you get is onion routing at the cellular radio layer. No single node sees both origin and destination. Chains rotate every 10 minutes. eSIM pools rotate on independent non-synchronized timers. Anyone can run a node. No registration, no fee, no central authority.

The components are all decades-old standards: GSM forwarding, GTP-U, private APNs, GSMA SGP.02, WireGuard. CAMO is the recognition that they compose into something that didn't formally exist before. The enforcement-resistance is structural, not designed. Disabling CAMO requires disabling private APNs and eSIM provisioning which collapses enterprise IoT globally. Tor protects the IP layer. CAMO protects the radio layer. They're complementary.

Spec, threat model, reference deployment: https://github.com/pablo-chacon/camo

CC BY 4.0.

you are viewing a single comment's thread
view the rest of the comments
[–] pablochacon@lemmy.ml 2 points 1 month ago

Well since this isn't a application I would say there's some work you need to do first. A good place to start is in this documentation: https://github.com/pablo-chacon/camo/blob/main/docs/mobile_onion_routing_spec.md

For something more "out of the box", I'm working on something but it's a different layer... And I have a few quirks to work out first.