geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shawn Jiang (JIRA)" <>
Subject [jira] Commented: (GERONIMO-4896) Commands to a Secure JMX Connector require the SSL keyStorePassword to be specified on command line
Date Fri, 26 Feb 2010 05:26:27 GMT


Shawn Jiang commented on GERONIMO-4896:

It would be appreciated if you can 

1, create patch based on current latest code.
2, use 4 space instead of tab as the indent in the patch.    
3, provide both 21, 22, trunk patches.   


> Commands to a Secure JMX Connector require the SSL keyStorePassword to be specified on
command line
> ---------------------------------------------------------------------------------------------------
>                 Key: GERONIMO-4896
>                 URL:
>             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,
> To my knowledge, it is not possible to run a Geronimo command (e.g. 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:
> and
> For example:
> {code}
> export GERONIMO_HOME=~/target/geronimo-jetty6-javaee5-2.2-SNAPSHOT
> export JAVA_OPTS="$GERONIMO_HOME/var/security/keystores/geronimo-default$GERONIMO_HOME/var/security/keystores/geronimo-default"
> $GERONIMO_HOME/bin/ -u system -p manager --secure list-modules --stopped
> {code}
> 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.

View raw message