More strict "allow reads for others" setting #108

New issue

Closed

opened 2025-12-28 18:07:06 +00:00 by sami · 1 comment

sami commented

2025-12-28 18:07:06 +00:00

Owner

Originally created by @roman-khimov on GitHub (Mar 28, 2024).

Originally assigned to: @mike-petrov on GitHub.

Current Behavior

"allow reads for others" sets two rules to allow GET and HEAD.

Expected Behavior

It should also allow RANGE and RANGEHASH. It should at the same time disable SEARCH/PUT/DELETE (these rules should come first).

Possible Solution

Fix rules.

Your Environment

Version of the product used: 0.5.1

Originally created by @roman-khimov on GitHub (Mar 28, 2024). Originally assigned to: @mike-petrov on GitHub. ## Current Behavior "allow reads for others" sets two rules to allow GET and HEAD. ## Expected Behavior It should also allow RANGE and RANGEHASH. It should at the same time disable SEARCH/PUT/DELETE (these rules should come first). ## Possible Solution Fix rules. ## Your Environment * Version of the product used: 0.5.1

sami

2025-12-28 18:07:06 +00:00

closed this issue
added the
S4

bug

I4

U1

security
labels

sami commented

2025-12-28 18:07:06 +00:00

Author

Owner

@roman-khimov commented on GitHub (Apr 17, 2024):

How to fix already existing containers:

open EACL management panel for your container
add PUT/DENY/OTHERS rule
add DELETE/DENY/OTHERS rule
save new EACL (this operation is free, no fees are paid)

Rule order doesn't matter in this case and SEARCH is optional (you can disable it as well or you can leave it available, your choice).

@roman-khimov commented on GitHub (Apr 17, 2024): How to fix already existing containers: * open EACL management panel for your container * add PUT/DENY/OTHERS rule * add DELETE/DENY/OTHERS rule * save new EACL (this operation is free, no fees are paid) Rule order doesn't matter in this case and SEARCH is optional (you can disable it as well or you can leave it available, your choice).