You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Napoleon Esmundo C. Ramirez (JIRA)" <ji...@codehaus.org> on 2008/04/28 16:15:47 UTC
[jira] Created: (MRELEASE-340) Don't store the scm password in
plaintext in release.properties
Don't store the scm password in plaintext in release.properties
---------------------------------------------------------------
Key: MRELEASE-340
URL: http://jira.codehaus.org/browse/MRELEASE-340
Project: Maven 2.x Release Plugin
Issue Type: Improvement
Reporter: Napoleon Esmundo C. Ramirez
Priority: Minor
The scm password is stored in plaintext in release.properties file. I think it would be safe not to save it there, then always prompt the user for the password every time.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-340) Don't store the scm password in
plaintext in release.properties
Posted by "Wendy Smoak (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=133568#action_133568 ]
Wendy Smoak commented on MRELEASE-340:
--------------------------------------
This can be a major issue in corporate environments with strict security rules.
In a single sign-on environment, exposing a password in plain text may compromise not only the source code repository, but all other systems the user has access to.
> Don't store the scm password in plaintext in release.properties
> ---------------------------------------------------------------
>
> Key: MRELEASE-340
> URL: http://jira.codehaus.org/browse/MRELEASE-340
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Reporter: Napoleon Esmundo C. Ramirez
> Priority: Minor
>
> The scm password is stored in plaintext in release.properties file. I think it would be safe not to save it there, then always prompt the user for the password every time.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-340) Don't store the scm password in
plaintext in release.properties
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=255561#action_255561 ]
Benjamin Bentmann commented on MRELEASE-340:
--------------------------------------------
Not sure since when but recent versions of the plugin support to read the credentials from the {{settings.xml}}, using the host name part of the SCM URL as the id to locate a {{<server>}} entry. AFAICT, this approach doesn't leak the passwords into the {{release.properties}}.
> Don't store the scm password in plaintext in release.properties
> ---------------------------------------------------------------
>
> Key: MRELEASE-340
> URL: http://jira.codehaus.org/browse/MRELEASE-340
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: scm
> Reporter: Nap Ramirez
> Priority: Minor
>
> The scm password is stored in plaintext in release.properties file. I think it would be safe not to save it there, then always prompt the user for the password every time.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MRELEASE-340) Don't store the scm password in
plaintext in release.properties
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter closed MRELEASE-340.
---------------------------------
Resolution: Duplicate
Assignee: Brett Porter
closed due to superceding issue
> Don't store the scm password in plaintext in release.properties
> ---------------------------------------------------------------
>
> Key: MRELEASE-340
> URL: https://jira.codehaus.org/browse/MRELEASE-340
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: scm
> Reporter: Nap Ramirez
> Assignee: Brett Porter
> Priority: Minor
>
> The scm password is stored in plaintext in release.properties file. I think it would be safe not to save it there, then always prompt the user for the password every time.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MRELEASE-340) Don't store the scm password in
plaintext in release.properties
Posted by "Arnaud Heritier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arnaud Heritier updated MRELEASE-340:
-------------------------------------
Component/s: scm
> Don't store the scm password in plaintext in release.properties
> ---------------------------------------------------------------
>
> Key: MRELEASE-340
> URL: http://jira.codehaus.org/browse/MRELEASE-340
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: scm
> Reporter: Napoleon Esmundo C. Ramirez
> Priority: Minor
>
> The scm password is stored in plaintext in release.properties file. I think it would be safe not to save it there, then always prompt the user for the password every time.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira