feat: finer-grained ACLs for server accesses #90
No reviewers
Labels
No labels
Compat/Breaking
Difficulty
Architectural
Difficulty
Easy
Difficulty
Hard
Help Wanted
Kind
Bug
Kind
Documentation
Kind
Enhancement
Kind
Feature
Kind
Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Security
Silenced Alert
Status
Abandoned
Status
Blocked
Status
Need More Info
Status
Postponed
Tracking Issue
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: the-distro/infra#90
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "acls"
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?
In the process of adding multi-tenant infrastructure, it seems relevant
to add finer-grained ACLs.
Related to #89.
Signed-off-by: Raito Bezarius masterancpp@gmail.com
Confirmed via
dry-activation
that this doesn't remove all SSH keys from the universe:/nix/store/bwj5af2f257azmir090g08d3jy2hvnma-root-authorized_keys
on public01.WIP: feat: finer-grained ACLs for server accessesto feat: finer-grained ACLs for server accessesDo we need all those invisible unicode characters?
we don't but i keep generating them for no reason
Well, other than that it looks a bit convoluted in how it reverses the group -> users and user -> groups mapping, but I guess it's fine
Hm, if you think it's better to go in another direction, I'm all for it ; it doesn't have to be merged that fast.
130faa2836
tof00bacd8fe
I re-inverted the logic, so it's less convoluted I hope. I will merge now because this has been staying for too long.
f00bacd8fe
to6d3e14ec27