mirror of
https://github.com/sigoden/dufs.git
synced 2026-04-08 16:49:02 +03:00
[GH-ISSUE #441] Seperate upload and delete permissions #240
Reference in New Issue
Block a user
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?
Originally created by @bonsairobo on GitHub (Aug 27, 2024).
Original GitHub issue: https://github.com/sigoden/dufs/issues/441
Specific Demand
I want to specify ACLs using seperate "upload" and "delete" permissions. This would allow me to have users that can upload to a directory without deleting anything.
Implementation suggestion
I think the simplest option would be to split the
wpermission intocandd, for create and delete. This could maintain backwards compatibility by makingwimplycd, but something likercwould only imply read and create, not delete.This scheme is a bit different from how the existing ACLs work though. As I understand it, there is only
roandrw. Soodoes not mean anything on its own. There might need to be specific handling of that for backwards compatibility.Another point worth considering is whether update and create should have separate permissions. Update also has the capacity to be destructive like a delete, just by overwriting a file with an empty byte array.
@sigoden commented on GitHub (Aug 27, 2024):
With
Upload without delete, you might encounter situations where incorrectly uploaded files cannot be deleted, and interrupted uploads can neither be resumed nor removed.@bonsairobo commented on GitHub (Aug 27, 2024):
AFAICT my only way to work around this is to have separate accounts and home directories for every user. Is it possible to update the dufs config file without restarting the service? This would let me build a dynamic user management service on top of dufs.
@sigoden commented on GitHub (Aug 27, 2024):
No plan
@bonsairobo commented on GitHub (Aug 27, 2024):
No plan to support config updates?
@sigoden commented on GitHub (Aug 27, 2024):
There's no plan to watch the configuration file for changes and restart the service.
This complicates things considerably without offering much benefit.