nostr-vpn

1# Nostr VPN
2 
3Use the `nvpn` CLI for private networking without a VPN provider account.
4Every device retains its own identity; network membership still needs an
5administrator's approval. This workflow does not require paid exits.
6 
7## Establish the execution context
8 
9- Run `nvpn --version`, `nvpn join-requests --help`, and
10  `nvpn join-request --help`. CLI approval and JSON join-request output are
11  currently source-only and have not yet shipped in a release. Install a matching
12  binary from https://github.com/mmalmi/nostr-vpn/releases/latest or use
13  `cargo install nvpn`. Check the release's supported architecture.
14- Choose an explicit, persistent absolute config path and pass `--config` on
15  every command, including elevated ones. Reuse a designated profile; never
16  overwrite an existing one with `init --force`.
17- A Linux tunnel needs network privileges, `/dev/net/tun`, and `iproute2`;
18  containers need `NET_ADMIN` and the TUN device. macOS/Windows need elevated
19  platform networking setup. A cloud terminal or plugin does not confer this
20  access. If unavailable, report that specific limitation and use an authorized
21  machine with those capabilities.
22- Persist config and key sidecars privately. Give separate devices separate
23  keys. Do not print private keys, copy the admin identity to a joining device,
24  or put join links into public output.
25 
26## Create or join
27 
28On a new admin host, run `nvpn init --config "$NVPN_CONFIG"`, then use the
29printed public `nostr_pubkey` with
30…