mirror of
https://github.com/nspcc-dev/neofs-s3-gw.git
synced 2026-03-01 04:29:15 +00:00
PutObject: object acl doesn't impose restrictions for a not-owner user #421
Labels
No labels
I2
I2
I3
I4
S2
S3
S4
S4
U0
U1
U2
U2
U3
U4
U4
auth-mate
blocked
bug
config
dependencies
discussion
documentation
enhancement
epic
feature
go
good first issue
help wanted
performance
question
security
test
tree-service
tree-service
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
nspcc-dev/neofs-s3-gw#421
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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 @evgeniiz321 on GitHub (Nov 11, 2023).
test_access_bucket_publicreadwrite_object_publicread
object acl:
logs:
@smallhive commented on GitHub (Feb 9, 2024):
According to https://github.com/nspcc-dev/neofs-s3-gw/issues/906#issue-1989038954 there is a conceptual difference between s3 and NeoFS.
IIRC inside NeoFS objects inherit bucket rules, which is why setting ACL for objects doesn't make sense in case of bucket ACL not so strict
@roman-khimov commented on GitHub (Jun 17, 2024):
But in S3 semantics it does. And we're doing everything via S3 gateway that can check for individual object ACLs.
@roman-khimov commented on GitHub (Jun 18, 2024):
S3 can check for them, but the problem is to create a NeoFS request that would somehow use per-object ACL. It can't.