You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Kings can now be started with --noise-private-key and --noise-public-key
to enable Noise protocol (NK pattern) encryption on rathole tunnels.
The public key is distributed to lings via council state, and lings
automatically enable encryption when connecting to keys that have one.
Copy file name to clipboardExpand all lines: readme.md
+9-1Lines changed: 9 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,15 @@ Controlplane application starting rathole servers, must be reachable for all rat
16
16
Dataplane application managing rathole clients and traefik proxies, can be completely isolated
17
17
18
18
### encryption
19
-
Since reverse tunnel and proxy encryption isn't implemented yet, it's highly recommended that network traffic encryption is handled via other mechanisms (e.g. [Nebula](https://github.com/slackhq/nebula) or VPN), unless you are absolutely sure your traffic will stay in-house
19
+
Rathole tunnel traffic between kings and lings can be encrypted using the [Noise protocol](https://noiseprotocol.org/) (NK pattern). Generate a keypair with `rathole --genkey` and pass the keys to the king:
20
+
21
+
```bash
22
+
king --noise-private-key="<base64-private-key>" --noise-public-key="<base64-public-key>" ...
23
+
```
24
+
25
+
The king sends its public key to the council, which distributes it to lings via state. Lings automatically enable encryption when connecting to kings that have a noise public key. Kings without noise keys continue to work unencrypted.
26
+
27
+
For proxy traffic or additional defense-in-depth, network-level encryption via [Nebula](https://github.com/slackhq/nebula) or VPN is still recommended.
0 commit comments