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

[Feature] Add Taildrop-Flag to Config #965

New Issue
Closed
opened 2025-12-29 02:26:47 +01:00 by adam · 5 comments
adam commented 2025-12-29 02:26:47 +01:00
Owner
Copy Link

Originally created by @lukaslindnermusic on GitHub (Mar 4, 2025).

Use case

If you don't want to use the feature, it might be better to just disable it as it bypasses ACLs.
There are usecases, where you want connections to be ONLY possible how defined in the ACLs whatsoever.

Description

Taildrop is currently activated by default and I think there is no way to disable it in Headscale.
However, the Tailscale Admin Console offers a toggle to disable it, so I think the best place to add this feature in headscale is the config file.

Contribution

  • I can write the design doc for this feature
  • I can contribute this feature

How can it be implemented?

I think, the best place for this setting might be the headscale config file.
It could be a simple flag, such as: enable_taildrop = true/false.

Originally created by @lukaslindnermusic on GitHub (Mar 4, 2025). ### Use case If you don't want to use the feature, it might be better to just disable it as it bypasses ACLs. There are usecases, where you want connections to be ONLY possible how defined in the ACLs whatsoever. ### Description Taildrop is currently activated by default and I think there is no way to disable it in Headscale. However, the Tailscale Admin Console offers a toggle to disable it, so I think the best place to add this feature in headscale is the config file. ### Contribution - [ ] I can write the design doc for this feature - [ ] I can contribute this feature ### How can it be implemented? I think, the best place for this setting might be the headscale config file. It could be a simple flag, such as: `enable_taildrop = true/false`.
adam added the enhancementno-stale-bot labels 2025-12-29 02:26:47 +01:00
adam closed this issue 2025-12-29 02:26:47 +01:00
adam commented 2025-12-29 02:26:48 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jun 3, 2025):

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

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

@lukaslindnermusic commented on GitHub (Jun 3, 2025):

No, please no stale label 😢

It still would be really nice, and maybe it even is in line with the planned changes regarding ACLs and tags, which also includes an issue where tagged devices can taildrop to user devices and vice-versa?

@lukaslindnermusic commented on GitHub (Jun 3, 2025): No, please no stale label 😢 It still would be really nice, and maybe it even is in line with the planned changes regarding ACLs and tags, which also includes an issue where tagged devices can taildrop to user devices and vice-versa?
adam commented 2025-12-29 02:26:48 +01:00
Author
Owner
Copy Link

@lukaslindnermusic commented on GitHub (Jun 3, 2025):

I also think that this is quite some problem.

If my tag:prod-server-tagged server can send files to my personal macbook, even if according to ACLs it should not be allowed to talk to anything by itself, and as Taildrop on macOS currently just blindly accepts what ever comes via Taildrop and just puts that in the Downloads folder automatically, I think this is quite a big issue.

@lukaslindnermusic commented on GitHub (Jun 3, 2025): I also think that this is quite some problem. If my `tag:prod-server`-tagged server can send files to my personal macbook, even if according to ACLs it should not be allowed to talk to anything by itself, and as Taildrop on macOS currently just blindly accepts what ever comes via Taildrop and just puts that in the Downloads folder automatically, I think this is quite a big issue.
adam commented 2025-12-29 02:26:48 +01:00
Author
Owner
Copy Link

@Volterxien commented on GitHub (Jul 4, 2025):

Bumping because I'd also like this to be both configurable and opt-in (disabled by default)

@Volterxien commented on GitHub (Jul 4, 2025): Bumping because I'd also like this to be both configurable and opt-in (disabled by default)
adam commented 2025-12-29 02:26:48 +01:00
Author
Owner
Copy Link

@nblock commented on GitHub (Dec 12, 2025):

Fixed via 642073f4b8

@nblock commented on GitHub (Dec 12, 2025): Fixed via 642073f4b87ccd1767ebe601fd18e0ef3d026b7b
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 no-stale-bot
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#965
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?