Repository navigation
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files
... and 2 files with indirect coverage changes @@ Coverage Diff @@
## development/9.3 #6332 +/- ##
================================================
Coverage 85.35% 85.36%
================================================
Files 207 207
Lines 13473 13480 +7
================================================
+ Hits 11500 11507 +7
Misses 1973 1973
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
leif-scality
left a comment
There was a problem hiding this comment.
A Deny on s3:VersionId now blocks copying that version, in bucket and IAM policies, and a repeated versionId in the copy source is rejected. I found no regressions. The new functional test fails without the fix and passes with it, and the stack's functional tests pass 20/20 against Vault 7.89.0. The other-spelling bypass stays in CLDSRV-1038, as the description says.
57d9720 to
5c5a75b
Compare
5c5a75b to
7a9b5bc
Compare
7a9b5bc to
647a09f
Compare
…sent - Use the copy source version ID as sent by the client, for both the bucket policy and the authorization request, instead of the internal version ID - Return InvalidArgument when the copy source versionId is repeated, so an array never reaches the bucket policy conditions
647a09f to
dd591e5
Compare
Hello tcarmet,My role is to assist you with the merge of this Available options
Available commands
Status report is not available. |
Request integration branchesWaiting for integration branch creation to be requested by the user. To request integration branches, please comment on this pull request with the following command: Alternatively, the |
A policy condition on
s3:VersionIdwas compared with the copy source's internal version ID instead of the version ID the client sent. So a Deny on a specific version blocked a GetObject of that version but not a copy of it, in both bucket and identity policies. The copy source's version ID is now evaluated as sent, like for a direct GetObject. A repeatedversionIdin the copy source is rejected, so it never reaches policy evaluation as a list. Version IDs that decode to the same version under different spellings are still not normalized; that's tracked in CLDSRV-1038 and affects GetObject the same way.Stacked on #6324.