Project

General

Profile

Actions

Bug #41042

closed

object can be copied to bucket from other user without writing permission

Added by Yonggang Hu over 4 years ago. Updated about 3 years ago.

Status:
Resolved
Priority:
High
Assignee:
-
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
luminous mimic nautilus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
rgw
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

There is a process of verifying writing permission for destination bucket in the source code, but it seems that the misplacement results in no execution.


Related issues 3 (0 open3 closed)

Copied to rgw - Backport #41633: luminous: object can be copied to bucket from other user without writing permissionRejectedActions
Copied to rgw - Backport #41634: nautilus: object can be copied to bucket from other user without writing permissionResolvedNathan CutlerActions
Copied to rgw - Backport #41635: mimic: object can be copied to bucket from other user without writing permissionResolvedNathan CutlerActions
Actions #1

Updated by Casey Bodley over 4 years ago

  • Status changed from New to Fix Under Review
  • Priority changed from Normal to High
  • Pull request ID set to 29628
Actions #2

Updated by Casey Bodley over 4 years ago

  • Status changed from Fix Under Review to Pending Backport
  • Backport set to luminous mimic nautilus
Actions #3

Updated by Nathan Cutler over 4 years ago

  • Copied to Backport #41633: luminous: object can be copied to bucket from other user without writing permission added
Actions #4

Updated by Nathan Cutler over 4 years ago

  • Copied to Backport #41634: nautilus: object can be copied to bucket from other user without writing permission added
Actions #5

Updated by Nathan Cutler over 4 years ago

  • Copied to Backport #41635: mimic: object can be copied to bucket from other user without writing permission added
Actions #6

Updated by Nathan Cutler over 4 years ago

  • Project changed from Ceph to rgw
Actions #7

Updated by Nathan Cutler about 3 years ago

  • Status changed from Pending Backport to Resolved

While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".

Actions

Also available in: Atom PDF