hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jakob Homan (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-7083) Allow SecureIO to be disabled for developer workstations
Date Mon, 03 Jan 2011 22:14:47 GMT

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

Jakob Homan updated HADOOP-7083:

    Priority: Major  (was: Trivial)

This is essentially adding a third state to Hadoop security: off, on and whatever-is-a-pain-for-developers-is-off.
 The jsvc requirements would also fall under this category.  This is not a trivial change
since misconfiguration could leave the system saying it's secure, when it's not.  Before this
goes in, I'd like to get the MR side of HADOOP-6822 in and provide information there, as well
as in a warning log message, that the JT/TT/etc are in essentially debug mode, to give a clue
as soon as possible.  Particularly so since the name of the new method, {{isInsecureDeveloperModeEnabled()}}
implies other aspects of security may be futzed with in the future (if this is not the intent,
the method name should be changed).

Note: this is not a code review.  A complete one is still required by before this may be committed.

> Allow SecureIO to be disabled for developer workstations
> --------------------------------------------------------
>                 Key: HADOOP-7083
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7083
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: native, security
>    Affects Versions: 0.22.0
>            Reporter: Todd Lipcon
>            Assignee: Alejandro Abdelnur
>         Attachments: hadoop-7083.txt
> In testing with secure Hadoop, the new requirement for native code is annoying on platforms
like OSX where the native code can be tricky to get compiled and working. We should allow
developers to disable this aspect of security by setting a special flag.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message