starred/headscale
1
0
Fork 0
mirror of https://github.com/juanfont/headscale.git synced 2026-01-11 20:00:28 +01:00
Code Issues 98 Packages Projects Releases 10 Wiki Activity

Split TLS options for gRPC and HTTP #622

New Issue
Closed
opened 2025-12-29 02:21:17 +01:00 by adam · 3 comments
adam commented 2025-12-29 02:21:17 +01:00
Owner
Copy Link

Originally created by @K3das on GitHub (Feb 2, 2024).

Why

Currently for a remote CLI you have no choice but to setup TLS. As a result, the public HTTP endpoints also end up encrypted, and in some configurations this sacrifices significant observability (currently my linkerd2 sidecar containers are unable to inspect traffic, monitor endpoint performance, and enforce per-route ACLs). While workarounds are possible (for example running headscale without TLS, and a proxy terminating TLS for gRPC), they would be far from ideal.

Description

One solution is adding split TLS options - to allow a user to enable TLS for gRPC, while not enabling it for other endpoints.

I'm happy to work on this if it's an acceptable change.

Originally created by @K3das on GitHub (Feb 2, 2024). ## Why Currently for a remote CLI you have no choice but to setup TLS. As a result, the public HTTP endpoints also end up encrypted, and in some configurations this sacrifices significant observability (currently my linkerd2 sidecar containers are unable to inspect traffic, monitor endpoint performance, and enforce per-route ACLs). While workarounds are possible (for example running headscale without TLS, and a proxy terminating TLS for gRPC), they would be far from ideal. ## Description One solution is adding split TLS options - to allow a user to enable TLS for gRPC, while not enabling it for other endpoints. I'm happy to work on this if it's an acceptable change.
adam added the enhancementstale labels 2025-12-29 02:21:17 +01:00
adam closed this issue 2025-12-29 02:21:17 +01:00
adam commented 2025-12-29 02:21:17 +01:00
Author
Owner
Copy Link

@ohdearaugustin commented on GitHub (Mar 15, 2024):

I see no issues if we split the configuration, as long it is a non breaking change.

@ohdearaugustin commented on GitHub (Mar 15, 2024): I see no issues if we split the configuration, as long it is a non breaking change.
adam commented 2025-12-29 02:21:18 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jun 13, 2024):

This issue is stale because it has been open for 90 days with no activity.

@github-actions[bot] commented on GitHub (Jun 13, 2024): This issue is stale because it has been open for 90 days with no activity.
adam commented 2025-12-29 02:21:18 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jun 21, 2024):

This issue was closed because it has been inactive for 14 days since being marked as stale.

@github-actions[bot] commented on GitHub (Jun 21, 2024): This issue was closed because it has been inactive for 14 days since being marked as stale.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
CLI
DERP
DNS
Nix
OIDC
SSH
bug
database
documentation
duplicate
enhancement
faq
good first issue
grants
help wanted
might-come
needs design doc
needs investigation
no-stale-bot
out of scope
performance
policy 📝
pull-request
Mirrored from GitHub Pull Request
 question
regression
routes
stale
tags
tailscale-feature-gap
well described ❤️
wontfix
No Label enhancement stale
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/headscale#622
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?