Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

acl: Perceive tombstone saving as delete operation #2748

Merged
merged 1 commit into from
Feb 27, 2024

Conversation

cthulhu-rider
Copy link
Contributor

No description provided.

Copy link

codecov bot commented Feb 21, 2024

Codecov Report

Attention: Patch coverage is 11.11111% with 8 lines in your changes are missing coverage. Please review.

Project coverage is 28.86%. Comparing base (9756cc4) to head (a7eb6ec).
Report is 2 commits behind head on master.

Files Patch % Lines
pkg/services/object/acl/v2/service.go 0.00% 8 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##           master    #2748      +/-   ##
==========================================
- Coverage   28.88%   28.86%   -0.03%     
==========================================
  Files         415      415              
  Lines       32478    32485       +7     
==========================================
- Hits         9382     9376       -6     
- Misses      22254    22265      +11     
- Partials      842      844       +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@cthulhu-rider cthulhu-rider force-pushed the 2261-put-tombstone-is-delete branch from 58cc445 to 0973b2e Compare February 21, 2024 21:58
Copy link
Member

@roman-khimov roman-khimov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Needs to be rebased onto 0.40.1, but looks good otherwise (needs a hell lot of testing though).

@cthulhu-rider cthulhu-rider force-pushed the 2261-put-tombstone-is-delete branch 3 times, most recently from e3f163f to 2816d8f Compare February 27, 2024 07:15
Previously, storage nodes handled `ObjectService.Put` requests
regardless of object types. Since writing tombstones is essentially an
operation of removing objects from their context, this opened up a
security issue: granting the right to write objects into the container
automatically granted the right to delete any objects from it. This, on
the one hand, implicit, on the other hand, strange behavior would raise
obvious questions about practical access control in the system.

From now, `PUT` ops of `TOMBSTONE` objects are treated as `DELETE`. The
only exclusion is intra-container replication that still should be
performed in `PUT` manner (container nodes have no removal rights).

Closes #2261.

Signed-off-by: Leonard Lyubich <[email protected]>
@cthulhu-rider cthulhu-rider force-pushed the 2261-put-tombstone-is-delete branch from 2816d8f to a7eb6ec Compare February 27, 2024 07:16
@roman-khimov roman-khimov merged commit 080a35d into master Feb 27, 2024
13 of 16 checks passed
@roman-khimov roman-khimov deleted the 2261-put-tombstone-is-delete branch February 27, 2024 14:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants