You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Mike Drob (JIRA)" <ji...@apache.org> on 2013/05/17 21:39:16 UTC

[jira] [Commented] (ACCUMULO-1412) Allow shell password to come from a variety of sources

    [ https://issues.apache.org/jira/browse/ACCUMULO-1412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13660984#comment-13660984 ] 

Mike Drob commented on ACCUMULO-1412:
-------------------------------------

I started working on this using JCommander (and got a functioning prototype) before realizing that the shell still uses Apache CLI. Is it worth refactoring to take advantage of some of the niceness of JCommander, considering that a bunch of the other utility classes already have made the switch in ACCUMULO-745
                
> Allow shell password to come from a variety of sources
> ------------------------------------------------------
>
>                 Key: ACCUMULO-1412
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1412
>             Project: Accumulo
>          Issue Type: Sub-task
>          Components: shell
>            Reporter: Mike Drob
>            Assignee: Mike Drob
>            Priority: Minor
>             Fix For: 1.6.0
>
>
> OpenSSL allows the user to read the password from a number of places, including a file, environment variable, file descriptor, command line argument, or standard in. It would be nice for accumulo to do the same, to ease scripting while still not revealing password through {{ps}} or it's brethren.
> A logical way to implement this might be using a [JCommander Custom Type|http://jcommander.org/#Custom_types] for the password field.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira