[GH-ISSUE #540] Support anonymous write access #313

New Issue

zhus · 2026-04-08T16:51:56+03:00

zhus commented

2026-04-08 16:51:56 +03:00

Originally created by @fredleger on GitHub (Feb 11, 2025).
Original GitHub issue: https://github.com/sigoden/dufs/issues/540

Specific Demand

Unless i made a mistake currently anonymous writes is not supported. Something like the following config will give you only read access to dir1and dir2

    auth:
      - '@/dir1:rw,/dir2:rw'

I'm facing a case where i put SSO before dufs (through k8s ingress and AWS ALB) and thus i don't need any kind of authentication.
I guess the same logic is applied for uploads, deltion etc...

Implement Suggestion

Allow end-user to setup RW access for anonymous error and enforce the default to avoid unwanted full open directory
It can also be done through an env variable like DUFS_ALLOW_ANONYMOUS_WRITES or DUFS_DISABLE_AUTH (because it's really what is is IMHO).

PS: thanks for the great tool ;-)

Originally created by @fredleger on GitHub (Feb 11, 2025). Original GitHub issue: https://github.com/sigoden/dufs/issues/540 ## Specific Demand Unless i made a mistake currently anonymous writes is not supported. Something like the following config will give you only *read* access to `dir1`and `dir2` ```yaml auth: - '@/dir1:rw,/dir2:rw' ``` I'm facing a case where i put SSO before dufs (through k8s ingress and AWS ALB) and thus i don't need any kind of authentication. I guess the same logic is applied for uploads, deltion etc... ## Implement Suggestion Allow end-user to setup RW access for anonymous error and enforce the default to avoid unwanted full open directory It can also be done through an env variable like `DUFS_ALLOW_ANONYMOUS_WRITES` or `DUFS_DISABLE_AUTH` (because it's really what is is IMHO). PS: thanks for the great tool ;-)

zhus closed this issue

2026-04-08 16:51:56 +03:00

zhus commented

2026-04-08 16:51:57 +03:00

@fredleger commented on GitHub (Feb 11, 2025):

for the record i also tried setting auth: [] in dufs.yaml and it's "worked". I have access in RW mode to all folder. So that can be a solution. But it allow full RW (not just the wanted dirs). In more complex scenario that can be a problem.

@fredleger commented on GitHub (Feb 11, 2025): for the record i also tried setting `auth: []` in `dufs.yaml` and it's "worked". I have access in RW mode to all folder. So that can be a solution. But it allow full RW (not just the wanted dirs). In more complex scenario that can be a problem.

zhus commented

2026-04-08 16:51:57 +03:00

@sigoden commented on GitHub (Feb 12, 2025):

Maybe you missed the options --allow-all or --allow-upload/--allow-delete.

@sigoden commented on GitHub (Feb 12, 2025): Maybe you missed the options `--allow-all` or `--allow-upload/--allow-delete`. ![Image](https://github.com/user-attachments/assets/6b2b5774-8af9-492e-b0f7-e727cffb08e2)

zhus commented

2026-04-08 16:51:57 +03:00

@fredleger commented on GitHub (Feb 12, 2025):

All these settings where set.

@fredleger commented on GitHub (Feb 12, 2025): All these settings where set.

zhus referenced this issue

2026-04-08 16:53:26 +03:00

[PR #313] [MERGED] refactor: change the value name of `--config` #561

Sign in to join this conversation.