From 707438f25e06a3c52b673b3df0daaa8f8428e543 Mon Sep 17 00:00:00 2001 From: Florian Preinstorfer Date: Tue, 18 Mar 2025 20:46:48 +0100 Subject: [PATCH] Mention that private keys generated if needed --- config-example.yaml | 12 +++++------- 1 file changed, 5 insertions(+), 7 deletions(-) diff --git a/config-example.yaml b/config-example.yaml index 50fd1edd..9d6b82d6 100644 --- a/config-example.yaml +++ b/config-example.yaml @@ -41,9 +41,9 @@ grpc_allow_insecure: false # The Noise section includes specific configuration for the # TS2021 Noise protocol noise: - # The Noise private key is used to encrypt the - # traffic between headscale and Tailscale clients when - # using the new Noise-based protocol. + # The Noise private key is used to encrypt the traffic between headscale and + # Tailscale clients when using the new Noise-based protocol. A missing key + # will be automatically generated. private_key_path: /var/lib/headscale/noise_private.key # List of IP prefixes to allocate tailaddresses from. @@ -91,10 +91,8 @@ derp: # For more details on how this works, check this great article: https://tailscale.com/blog/how-tailscale-works/ stun_listen_addr: "0.0.0.0:3478" - # Private key used to encrypt the traffic between headscale DERP - # and Tailscale clients. - # The private key file will be autogenerated if it's missing. - # + # Private key used to encrypt the traffic between headscale DERP and + # Tailscale clients. A missing key will be automatically generated. private_key_path: /var/lib/headscale/derp_server_private.key # This flag can be used, so the DERP map entry for the embedded DERP server is not written automatically,