Cannot access S3 bucket root when the access policy checks for empty prefix#111
Open
martinprikryl wants to merge 1 commit intobji:masterfrom
Open
Cannot access S3 bucket root when the access policy checks for empty prefix#111martinprikryl wants to merge 1 commit intobji:masterfrom
martinprikryl wants to merge 1 commit intobji:masterfrom
Conversation
…prefix
When accessing bucket root, AWS tools send empty prefix (prefix=), contrary to libs3 that sends no prefix. But some AWS policy examples suggest conditions like:
"Condition":{"StringEquals":{"s3:prefix":["","home/"],"s3:delimiter":["/"]}}
With such conditions libs3 will fail to access the root.
Reported for WinSCP:
https://winscp.net/forum/viewtopic.php?t=31359
The same problem for Cyberduck:
https://trac.cyberduck.io/ticket/11549
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When accessing bucket root, AWS tools send empty prefix (prefix=), contrary to libs3 that sends no prefix. But some AWS policy examples suggest conditions like:
"Condition":{"StringEquals":{"s3:prefix":["","home/"],"s3:delimiter":["/"]}}
With such conditions libs3 will fail to access the root.
Reported for WinSCP:
https://winscp.net/forum/viewtopic.php?t=31359
The same problem for Cyberduck:
https://trac.cyberduck.io/ticket/11549