[JIRA] [perforce] (JENKINS-19794) Prevent password exposure in perforce

Sat, 23 Nov 2013 11:30:23 -0800

I agree that such retention of initial configs is a better way, but I don't think that such control should not appear in the main section in order to save some space on configuration pages.

BTW, I still think that the option is highly insecure, so it is preferable to prohibit it and propose usage of "Mask Passwords" plugin instead. It makes sense to describe such approach in the proposed warning message.

I propose the following approach:

  • I'll fix the change to allow editing of "Expose P4PASSWD to environmen" configuration in any case
  • If the global option is enabled, this section will be available in advanced section
  • All changes will be saved to job configuration

Do you agree with such approach?
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to