You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Steve Loughran (Jira)" <ji...@apache.org> on 2020/04/07 13:05:00 UTC
[jira] [Resolved] (HADOOP-16482) S3A doesn't actually verify paths
have the correct authority
[ https://issues.apache.org/jira/browse/HADOOP-16482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Loughran resolved HADOOP-16482.
-------------------------------------
Fix Version/s: 3.3.0
Assignee: Steve Loughran
Resolution: Duplicate
HADOOP-15430 covers this
> S3A doesn't actually verify paths have the correct authority
> ------------------------------------------------------------
>
> Key: HADOOP-16482
> URL: https://issues.apache.org/jira/browse/HADOOP-16482
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.1.0
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Major
> Fix For: 3.3.0
>
>
> Probably been around a *long* time, but we've never noticed, assuming that {{Path.makeQualified(uri, workingDir)}} did the right thing.
> You can provide any s3a URI to an S3 command and it'll get mapped to the current bucket without any validation that the authorities are equal. Oops.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org