summaryrefslogtreecommitdiff
path: root/3 Resources/Tailscale.md
diff options
context:
space:
mode:
authorJasper Ras <jras@hostnet.nl>2025-03-20 11:07:49 +0100
committerJasper Ras <jras@hostnet.nl>2025-03-20 11:07:49 +0100
commit80ccf68f55dbb70d7e5ed52ee95b3c9d1b6ce264 (patch)
tree93e28e85ab70052aa6f577998ec7dc1f413b40c0 /3 Resources/Tailscale.md
parent9642cd7ae24f0ba79ce5647c709b35ae8f06a285 (diff)
vault backup: 2025-03-20 11:07:48
Diffstat (limited to '3 Resources/Tailscale.md')
-rw-r--r--3 Resources/Tailscale.md16
1 files changed, 16 insertions, 0 deletions
diff --git a/3 Resources/Tailscale.md b/3 Resources/Tailscale.md
new file mode 100644
index 0000000..6cf82c4
--- /dev/null
+++ b/3 Resources/Tailscale.md
@@ -0,0 +1,16 @@
+---
+tags:
+ - tailscale
+ - vpn
+references:
+ - https://tailscale.com/blog/tailscale-key-management
+---
+# About keys
+Two types of keys: machine keys and node keys.
+
+The machine key is tied to a specific machine and is used during pre-authorization (started when it first attempts to join a network).
+
+When successfully added to a network a node key is generated on the client. The public component is tied to the machine key on the control server.
+The node key is also tied to an identity; via the URL that's sent back to the client and then used to login.
+
+The public node key is then distributed to other nodes it's allowed to communicate with. \ No newline at end of file