You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Kevan Miller (JIRA)" <ji...@apache.org> on 2009/11/18 05:04:39 UTC

[jira] Assigned: (GERONIMO-4927) keystorePass attribute on TomcatWebSSLConnector GBean should be encrypted/obscured

     [ https://issues.apache.org/jira/browse/GERONIMO-4927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kevan Miller reassigned GERONIMO-4927:
--------------------------------------

    Assignee: Kevan Miller

> 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
>            Assignee: Kevan Miller
>             Fix For: 2.1.5
>
>         Attachments: 4927.patch
>
>
> 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.