[ 
https://issues.apache.org/jira/browse/GERONIMO-4896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798643#action_12798643
 ] 

Ashish Jain commented on GERONIMO-4896:
---------------------------------------

Uploading  a new patch following has been incorporated

1) Read encrypted  passwords from a file.
2) If using default keystore and truststore than no need to specify location of 
keystore or truststore.
3) In case a custom location than you need to specify the correct location 
through JAVA_OPTS.
4) Specify the file location of the password file using the following system 
property 
org.apache.geronimo.keyStoreTrustStorePasswordFile. This will make geronoimo 
find the file
for password.

The deploy tool encrypted utility "deploy.bat encrypt" has been used to encrypt 
password. Refer GERONIMO-3003.



> Commands to a Secure JMX Connector require the SSL keyStorePassword to be 
> specified on command line
> ---------------------------------------------------------------------------------------------------
>
>                 Key: GERONIMO-4896
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-4896
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>    Affects Versions: 2.1.5, 2.2, 3.0
>            Reporter: Kevan Miller
>            Assignee: Ashish Jain
>             Fix For: 2.1.5, 3.0, Wish List
>
>         Attachments: 4896.patch, 4896_updated.patch, JavaAgent.jar, 
> JvmOpts.java
>
>
> To my knowledge, it is not possible to run a Geronimo command (e.g. deploy.sh 
> deploy or gsh geronimo/stop-server) to a server with a secure JMX Connector 
> (running SSL, without specifying the following Java system properties on the 
> command line:
>    javax.net.ssl.keyStore and javax.net.ssl.keyStorePassword
> For example:
> {code}
> export GERONIMO_HOME=~/target/geronimo-jetty6-javaee5-2.2-SNAPSHOT
> export 
> JAVA_OPTS="-Djavax.net.ssl.keyStore=$GERONIMO_HOME/var/security/keystores/geronimo-default
>  -Djavax.net.ssl.keyStorePassword=secret 
> -Djavax.net.ssl.trustStore=$GERONIMO_HOME/var/security/keystores/geronimo-default
>  -Djavax.net.ssl.trustStorePassword=secret"
> $GERONIMO_HOME/bin/deploy.sh -u system -p manager --secure list-modules 
> --stopped
> {code}
> javax.net.ssl.keyStorePassword causes a problem, since this means the 
> keyStorePassword is available, in-the-clear, to someone inspecting executing 
> processes. For example while a deploy command was active, someone could run 
> 'ps auxww | grep deployer.jar' and discover the keyStorePassword for the 
> KeyStore.
> Geronimo should provide a mechanism, whereby users can specify the 
> keyStorePassword without making that secret available to anyone inspecting 
> processes running on the current system. Ideally, the password could be 
> encrypted/obfuscated within a file (just as passwords can be 
> encrypted/obfuscated in var/config/config.xml).

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

Reply via email to