Uploaded image for project: 'Ranger'
  1. Ranger
  2. RANGER-1707

Update RangerHdfsAuthorizer for changes in traverse checks since Hadoop 2.8

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 1.0.0
    • 1.0.0
    • plugins
    • Patch

    Description

      Traversal check in RangerHdfsAuthorizer works incorrectly, when it is asked for access to /a/b/c.txt, it only checks that if there are a policy which grants EXEC to /a/b, but if it there aren't any, then it doesn't check, if there is a policy which grants READ, WRITE or EXEC to /a/b/c.txt explicitly, which would mean, that the path is accessible to the user.
      This hasn't noticed by the current unit tests, because HDFS before 2.8.0 doesn't called the traversal check before reading or writing a file, however it will cause problem with 2.8.0, where FSDirectory.resolvePath will perform a mandatory traversal check.

      Attachments

        1. RANGER-1707-3.patch
          19 kB
          Zsombor Gegesy
        2. RANGER-1707-2.patch
          19 kB
          Zsombor Gegesy
        3. 0001-RANGER-1707-Fix-hdfs-traverse-check-which-problem-wa.patch
          18 kB
          Zsombor Gegesy

        Issue Links

          Activity

            People

              abhayk Abhay Kulkarni
              zsombor Zsombor Gegesy
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: