hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-10511) s3n:// incorrectly handles URLs with secret keys that contain a slash
Date Fri, 06 Feb 2015 21:38:35 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-10511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Steve Loughran updated HADOOP-10511:
------------------------------------
    Status: Patch Available  (was: Open)

Patch -002; patch 001 against trunk.

Jenkins will not catch it as it doesn't run the s3 tests, but this patch will fail the s3
tests. Presumably the new test needs to go down into the {{TestInMemoryNativeS3FileSystemContract}}
test as in {{Jets3tNativeS3FileSystemContractTest}} it gets rejected by AWS

> s3n:// incorrectly handles URLs with secret keys that contain a slash
> ---------------------------------------------------------------------
>
>                 Key: HADOOP-10511
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10511
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: fs/s3
>            Reporter: Daniel Darabos
>         Attachments: HADOOP-10511-002.patch, HADOOP-10511.patch
>
>
> This is similar to HADOOP-3733, but happens on s3n:// instead of s3://.
> Essentially if I have a path like "s3n://key:pass%2Fword@example.com/test", it will under
certain circumstances be replaced with "s3n://key:pass/test" which then causes "Invalid hostname
in URI" exceptions.
> I have a unit test and a fix for this. I'll make a pull request in a moment.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message