Uploaded image for project: 'Hadoop Common'
  1. Hadoop Common
  2. HADOOP-14022

S3 connections fails if in-URI AWS secret key contains '+' and '/' both

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Duplicate
    • Affects Version/s: 2.7.3
    • Fix Version/s: None
    • Component/s: fs/s3
    • Labels:
      None

      Description

      Hi Guys,

      I am opening a bug here. I am pretty sure it was fixed but I believe this is still the case.

      Our secret key contains a "/" and "+" both and it seems all the cases fail and keep producing the following error :

      IllegalArgumentException: The bucketName parameter must be specified.

      I would like to know if that is still the case.

      Check old issue here : https://issues.apache.org/jira/browse/HADOOP-13287

        Issue Links

          Activity

          Hide
          stevel@apache.org Steve Loughran added a comment -

          Simply the aggregate of HADOOP-13287 and HADOOP-3733

          1. you need to escape these
          2. you SHOULD NOT stick AWS secrets in URIs, as they get logged in lots of code which does not consider that Path variables could contain secrets.

          Hadoop 2.8 will warn you from doing this; with per-bucket configs the sole defensible case "cross-account access" has gone. Please don't.

          Show
          stevel@apache.org Steve Loughran added a comment - Simply the aggregate of HADOOP-13287 and HADOOP-3733 you need to escape these you SHOULD NOT stick AWS secrets in URIs, as they get logged in lots of code which does not consider that Path variables could contain secrets. Hadoop 2.8 will warn you from doing this; with per-bucket configs the sole defensible case "cross-account access" has gone. Please don't.

            People

            • Assignee:
              Unassigned
              Reporter:
              pinkencryption pinkencryption
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development