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

[PR #311] [MERGED] Issues with current ACL implementation and solution proposal #1374

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

📋 Pull Request Information

Original PR: https://github.com/juanfont/headscale/pull/311
Author: @restanrm
Created: 2/8/2022
Status: ✅ Merged
Merged: 3/8/2022
Merged by: @kradalby

Base: main ← Head: docs-acl-modifications

📝 Commits (9)

  • 85cf443 docs(acls): Issues with ACL and proposition
  • 0426212 docs(acls): add example use case
  • 7bdd774 fix(acl): add missing internal namespace communications
  • 86b329d chore(docs): create proposals directory
  • e540679 docs(acl-proposals): integrate comments
  • c364c2a chore(acl-proposals): apply prettier
  • 55d746d docs(acls-proposal): wording comment
  • 397b6fc Merge branch 'main' into docs-acl-modifications
  • dd219d0 Merge branch 'main' into docs-acl-modifications

📊 Changes

1 file changed (+362 additions, -0 deletions)

View changed files

➕ docs/proposals/001-acls.md (+362 -0)

📄 Description

This pull request is not really meant to be merged, but to try and explain the issues with the current ACL's and propose an alternative. This was discussed with @kradalby on discord.

I hope that the issue is correctly explained.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/juanfont/headscale/pull/311 **Author:** [@restanrm](https://github.com/restanrm) **Created:** 2/8/2022 **Status:** ✅ Merged **Merged:** 3/8/2022 **Merged by:** [@kradalby](https://github.com/kradalby) **Base:** `main` ← **Head:** `docs-acl-modifications` --- ### 📝 Commits (9) - [`85cf443`](https://github.com/juanfont/headscale/commit/85cf443ac6290022edd688e579d954516d0e3ec6) docs(acls): Issues with ACL and proposition - [`0426212`](https://github.com/juanfont/headscale/commit/04262123483f1294d52d22f0451c9d05a4b753f9) docs(acls): add example use case - [`7bdd774`](https://github.com/juanfont/headscale/commit/7bdd7748e4cec82206369d972240363bca644527) fix(acl): add missing internal namespace communications - [`86b329d`](https://github.com/juanfont/headscale/commit/86b329d8bfeb5af56d847b3085ac286cbf935676) chore(docs): create proposals directory - [`e540679`](https://github.com/juanfont/headscale/commit/e540679dbd6d4d9d11d9838ecf6e522d3d8a9a04) docs(acl-proposals): integrate comments - [`c364c2a`](https://github.com/juanfont/headscale/commit/c364c2a38206855ad8bbf7264d687cf09c0c40cd) chore(acl-proposals): apply prettier - [`55d746d`](https://github.com/juanfont/headscale/commit/55d746d3f5323f661238db9ecb2da93ad95e7430) docs(acls-proposal): wording comment - [`397b6fc`](https://github.com/juanfont/headscale/commit/397b6fc4bf9920d0f6f1ddd2e2f9c2d86093e9b0) Merge branch 'main' into docs-acl-modifications - [`dd219d0`](https://github.com/juanfont/headscale/commit/dd219d0ff60cbcc0f11ac9ae76e239c93b17d021) Merge branch 'main' into docs-acl-modifications ### 📊 Changes **1 file changed** (+362 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `docs/proposals/001-acls.md` (+362 -0) </details> ### 📄 Description This pull request is not really meant to be merged, but to try and explain the issues with the current ACL's and propose an alternative. This was discussed with @kradalby on discord. I hope that the issue is correctly explained. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
adam added the pull-request label 2025-12-29 02:29:51 +01:00
adam closed this issue 2025-12-29 02:29:51 +01:00
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 pull-request
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#1374
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?