|
||||||||
|
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.
on slave, as the file only exists during the build and get deleted by CleanTempFileAction this isn't an issue to get content in clear text.
The issue here is about storing raw config file on master. A malicious user then can just view them to get your secrets. If config file content is encrypted (obfuscated would be a better term) this limit impact for storing passwords there.
Other (more complex) option could be to support variable expansion in config file, and let credentials plugin manage secret informations into settings content. This would then be "flatten" when sent to slave during a build.