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

Christopher Tubbs commented on ACCUMULO-1276:
---------------------------------------------

[~billie.rinaldi] said:
{quote}Actually – I might go as far as to say that the script is just for easy 
development / testing. We could document it as such, or get rid of it.{quote}

I agree. If we had an integration test for testing the monitor, that leveraged 
maven-keytool-plugin to generate the certificate in an automated way, I'd say 
we get rid of it.

Also, if it's just for development/testing/documentation purposes, there's 
really no reason to bother with the generating of the password... it could just 
be "password". (At the very least, there's no reason to lose system entropy for 
testing.)

[~medined] said:
{quote}Once the process is documented, the need for the script would be 
reduced.{quote}
We just need to document what kind of certificates we accept and how to 
configure them. Documenting the process to generate these certificates should 
be left to their respective tools/websites (openssl, keytool, etc.).
                
> problems running generate_monitor_certificate.sh
> ------------------------------------------------
>
>                 Key: ACCUMULO-1276
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1276
>             Project: Accumulo
>          Issue Type: Bug
>          Components: scripts
>    Affects Versions: 1.4.3
>            Reporter: David Medinets
>            Assignee: Eric Newton
>
> I tried to run the generate_monitor_certificate.sh script on an Ubuntu VM
> and saw the following message:
> root@li459-74:/usr/local/accumulo# bin/generate_monitor_certificate.sh
> tail: cannot open `+2' for reading: No such file or directory
> I briefly looked into the script but don't know enough about /dev/random to
> debug much.

--
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

Reply via email to