geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ashish Jain (JIRA)" <j...@apache.org>
Subject [jira] Commented: (GERONIMO-4927) keystorePass attribute on TomcatWebSSLConnector GBean should be encrypted/obscured
Date Tue, 03 Nov 2009 11:09:01 GMT

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

Ashish Jain commented on GERONIMO-4927:
---------------------------------------

Can we not rename the existing attribute as keystorePassword? Or else 
add another line of code in org.apache.geronimo.system.configuration.GBeanOverride.writeXml
 to encrypt the keystorePass adding
some logic for example indexof('pass") than do the encryption

> keystorePass attribute on TomcatWebSSLConnector GBean should be encrypted/obscured
> ----------------------------------------------------------------------------------
>
>                 Key: GERONIMO-4927
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-4927
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>    Affects Versions: 2.1.5, 2.2
>            Reporter: Kevan Miller
>             Fix For: 2.1.5, 2.2.1, 3.0
>
>
> keystorePass does not conform to the current convention for encrypting/obscuring GBean
attributes. Currently, attribute names with 'password' will be encrypted. 
> We should either recognize keystorePass as an attribute requiring encryption or add a
new keystorePassword attribute and start using that (with some appropriate migration logic,
if a 'keystorePass' is configured). I guess I prefer the latter option. Other opinions? 

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