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

Unclear sentences in documentation about ACLs #677

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

Originally created by @dariusarnold on GitHub (Mar 20, 2024).

Bug description

The following document contains the sentence

For instance, instead of referring to users when defining groups you must use users (which are the equivalent to user/logins in Tailscale.com).

The sentence is confusing and probably one of the mentions of user is wrong. I think what is meant that instead of defining groups made of users and using the groups for ACL, the users are used directly on the ACL.

When using ACL's the User borders are no longer applied. All machines whichever the User have the ability to communicate with other hosts as long as the ACL's permits this exchange.

Borders are only used once here and not explained. I am having issues understanding what the sentence is supposed to mean. The official Tailscale doc about ACLs doesn't mention borders, but I am not overly familiar with tailscale/headscale, so it might be a common term. I understand this to mean using ACLs allows communication between machines despite them not belonging to the same user account. Is that not possible when ACLs are not in use?

Environment

On the headscale main branch, file was last changed with commit a6bc792a61.

Originally created by @dariusarnold on GitHub (Mar 20, 2024). ## Bug description The [following document](docs/acls.md) contains the sentence > For instance, instead of referring to users when defining groups you must use users (which are the equivalent to user/logins in Tailscale.com). The sentence is confusing and probably one of the mentions of user is wrong. I think what is meant that instead of defining groups made of users and using the groups for ACL, the users are used directly on the ACL. > When using ACL's the User borders are no longer applied. All machines whichever the User have the ability to communicate with other hosts as long as the ACL's permits this exchange. Borders are only used once here and not explained. I am having issues understanding what the sentence is supposed to mean. The official Tailscale doc about ACLs doesn't mention borders, but I am not overly familiar with tailscale/headscale, so it might be a common term. I understand this to mean using ACLs allows communication between machines despite them not belonging to the same user account. Is that not possible when ACLs are not in use? ## Environment On the headscale main branch, file was last changed with commit https://github.com/juanfont/headscale/commit/a6bc792a6130dbfdc88b2436b790e542ea17ceba.
adam added the stalebugdocumentationpolicy 📝 labels 2025-12-29 02:21:57 +01:00
adam closed this issue 2025-12-29 02:21:57 +01:00
adam commented 2025-12-29 02:21:58 +01:00
Author
Owner
Copy Link

@allamedo commented on GitHub (Apr 6, 2024):

In the ACLs documentation there is also a reference to the ./tests/acls/ directory that doesn't seem to exist anymore.

@allamedo commented on GitHub (Apr 6, 2024): In the ACLs documentation there is also a reference to the `./tests/acls/` directory that doesn't seem to exist anymore.
adam commented 2025-12-29 02:21:58 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Aug 7, 2024):

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

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

@github-actions[bot] commented on GitHub (Aug 14, 2024):

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

@github-actions[bot] commented on GitHub (Aug 14, 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 bug documentation policy 📝 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#677
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?