geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chi Runhua (JIRA)" <j...@apache.org>
Subject [jira] Commented: (GERONIMO-4896) Commands to a Secure JMX Connector require the SSL keyStorePassword to be specified on command line
Date Thu, 25 Feb 2010 13:47:28 GMT

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

Chi Runhua commented on GERONIMO-4896:
--------------------------------------

User deserves better description or instructions instead of an exception when the original
command line doesn't work properly on the new release. 

I'd like to see description like the following aside with the exception:

{noformat}
The usage of javax.net.ssl.keyStorePassword and javax.net.ssl.trustStorePassword in a command
line has been deprecated. 
Use org.apache.geronimo.keyStoreTrustStorePasswordFile property to specify the location of
passwords of the trustStore and keystore. 
{noformat}

Any comments?


> 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: Shawn Jiang
>             Fix For: 2.1.5, 3.0, Wish List
>
>         Attachments: 4896.patch, 4896_updated.patch, 4896_updated_21.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.


Mime
View raw message