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

[Feature] Taildrop between users #829

New Issue
Closed
opened 2025-12-29 02:24:35 +01:00 by adam · 1 comment
adam commented 2025-12-29 02:24:35 +01:00
Owner
Copy Link

Originally created by @ENGO150 on GitHub (Oct 12, 2024).

Use case

Hey! I use Taildrop really often, but one thing that keeps it from being perfect (at least for me) is sharing a file between nodes of two users... For instance when I want to send my colleague something on Tailnet.

I have tried looking through Headscale source, but I didn't find anything about the limitation.


I have no idea if headscale can change this or if this is fully rooted in Tailscale.

Description

It would be great to be able to allow file sharing using Taildrop between users.

Contribution

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

How can it be implemented?

I can think of three ways of allowing the shared Taildrop

  • Allowing it in headscale config file
    • shared_taildrop: bool
  • Setting it using headscale command
    • headscale file shared and headscale file private
  • Setting the Taildrop to be shared by default and using ACLs instead
"nodeAttrs":
 [
     {
         "target": ["*"],
         "attr":
         [
             "file:share"
         ]
     }
 ]
Originally created by @ENGO150 on GitHub (Oct 12, 2024). ### Use case Hey! I use Taildrop really often, but one thing that keeps it from being perfect (at least for me) is sharing a file between nodes of two users... For instance when I want to send my colleague something on Tailnet. I have tried looking through Headscale source, but I didn't find anything about the limitation. <br> **I have no idea if headscale can change this or if this is fully rooted in Tailscale.** ### Description It would be great to be able to allow file sharing using Taildrop between users. ### Contribution - [X] I can write the design doc for this feature - [X] I can contribute this feature ### How can it be implemented? I can think of three ways of allowing the shared Taildrop - Allowing it in headscale config file - `shared_taildrop: bool` - Setting it using headscale command - `headscale file shared` and `headscale file private` - Setting the Taildrop to be shared by default and using ACLs instead ``` "nodeAttrs": [ { "target": ["*"], "attr": [ "file:share" ] } ] ```
adam added the enhancement label 2025-12-29 02:24:35 +01:00
adam closed this issue 2025-12-29 02:24:35 +01:00
adam commented 2025-12-29 02:24:36 +01:00
Author
Owner
Copy Link

@nblock commented on GitHub (Oct 13, 2024):

According to this Tailscale forum post it is currently not possible; here is a Tailscale bug report.

@nblock commented on GitHub (Oct 13, 2024): According to [this Tailscale forum post](https://forum.tailscale.com/t/taildrop-files-between-users/1854) it is currently not possible; here is a [Tailscale bug report](https://github.com/tailscale/tailscale/issues/2101).
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
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#829
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?