Uploaded image for project: 'Hadoop YARN'
  1. Hadoop YARN
  2. YARN-2198

Remove the need to run NodeManager as privileged account for Windows Secure Container Executor

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.6.0
    • Component/s: None
    • Labels:
    • Target Version/s:
    • Hadoop Flags:
      Reviewed

      Description

      YARN-1972 introduces a Secure Windows Container Executor. However this executor requires the process launching the container to be LocalSystem or a member of the a local Administrators group. Since the process in question is the NodeManager, the requirement translates to the entire NM to run as a privileged account, a very large surface area to review and protect.

      This proposal is to move the privileged operations into a dedicated NT service. The NM can run as a low privilege account and communicate with the privileged NT service when it needs to launch a container. This would reduce the surface exposed to the high privileges.

      There has to exist a secure, authenticated and authorized channel of communication between the NM and the privileged NT service. Possible alternatives are a new TCP endpoint, Java RPC etc. My proposal though would be to use Windows LPC (Local Procedure Calls), which is a Windows platform specific inter-process communication channel that satisfies all requirements and is easy to deploy. The privileged NT service would register and listen on an LPC port (NtCreatePort, NtListenPort). The NM would use JNI to interop with libwinutils which would host the LPC client code. The client would connect to the LPC port (NtConnectPort) and send a message requesting a container launch (NtRequestWaitReplyPort). LPC provides authentication and the privileged NT service can use authorization API (AuthZ) to validate the caller.

        Attachments

        1. YARN-2198.1.patch
          101 kB
          Remus Rusanu
        2. YARN-2198.2.patch
          102 kB
          Remus Rusanu
        3. YARN-2198.separation.patch
          295 kB
          Remus Rusanu
        4. YARN-2198.3.patch
          149 kB
          Remus Rusanu
        5. YARN-2198.delta.4.patch
          235 kB
          Remus Rusanu
        6. YARN-2198.trunk.4.patch
          240 kB
          Remus Rusanu
        7. YARN-2198.delta.5.patch
          216 kB
          Remus Rusanu
        8. YARN-2198.trunk.5.patch
          240 kB
          Remus Rusanu
        9. YARN-2198.delta.6.patch
          219 kB
          Remus Rusanu
        10. YARN-2198.trunk.6.patch
          241 kB
          Remus Rusanu
        11. YARN-2198.delta.7.patch
          230 kB
          Remus Rusanu
        12. YARN-2198.trunk.8.patch
          222 kB
          Remus Rusanu
        13. YARN-2198.trunk.9.patch
          222 kB
          Remus Rusanu
        14. YARN-2198.trunk.10.patch
          275 kB
          Remus Rusanu
        15. .YARN-2198.delta.10.patch
          253 kB
          Remus Rusanu
        16. YARN-2198.11.patch
          259 kB
          Remus Rusanu
        17. YARN-2198.12.patch
          259 kB
          Remus Rusanu
        18. YARN-2198.13.patch
          260 kB
          Remus Rusanu
        19. YARN-2198.14.patch
          260 kB
          Remus Rusanu
        20. YARN-2198.15.patch
          262 kB
          Remus Rusanu
        21. YARN-2198.16.patch
          262 kB
          Remus Rusanu

          Issue Links

            Activity

              People

              • Assignee:
                rusanu Remus Rusanu
                Reporter:
                rusanu Remus Rusanu
              • Votes:
                0 Vote for this issue
                Watchers:
                12 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: