Actions
Bug #59508
opens3cmd set-acl --acl-public (maybe?) doesn't work
Status:
New
Priority:
Low
Assignee:
-
Target version:
-
% Done:
0%
Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
Creating a bucket with a public acl allows other users to access it:
s3cmd mb --acl-public s3://test2
s3cmd put .gtwsrc s3://test2/testobject
s3cmd ls --access_key="NOPQRSTUVWXYZABCDEFG" --secret_key="nopqrstuvwxyzabcdefghijklmnabcdefghijklm" -l s3://test2
2023-04-21 17:37 2673 90ee391bc396a15d9d73b5d124e6b034 STANDARD s3://test2/testobject
However, if the bucket is made normally, and the ACL is changed with:
s3cmd setacl --acl-public s3://test
then the other user get's permission denied. I have not investigated why this is yet, but I thought I'd open this to make sure it doesn't slip through the cracks.
No data to display
Actions