You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[JENKINS-911] Alternate Launcher.launch that hides passwords on command line #866
The current implementations of Launcher.launch(...)
all print the command line verbatim to the log.
When the command line includes a password, this is not good.
A second Launcher.launch(...) method which would allow the caller to **** out
the info that goes to the log files to make password snooping more difficult
The current implementations of Launcher.launch(...)
all print the command line verbatim to the log.
When the command line includes a password, this is not good.
A second Launcher.launch(...) method which would allow the caller to **** out
the info that goes to the log files to make password snooping more difficult
It's a reasonable request but using passwords on command line arguments is
really insecure anyway — you still get to see them through /proc, pargs,
process explorer, etc.
It's a reasonable request but using passwords on command line arguments is
really insecure anyway — you still get to see them through /proc, pargs,
process explorer, etc.
/proc etc. are visible only to people logged in on the same machine (with
appropriate permissions). Quite different from a build log exposed via the web.
/proc etc. are visible only to people logged in on the same machine (with
appropriate permissions). Quite different from a build log exposed via the web.
I have added one approach for the necessary methods to Launcher.launch, added
javadoc warning that these methods only help with the build log, and updated the
change log to reflect this.
Target 1.147
I have added one approach for the necessary methods to Launcher.launch, added
javadoc warning that these methods only help with the build log, and updated the
change log to reflect this.
Activity
jenkins-infra-bot commentedon Oct 15, 2007
Raw content of original comment:
It's a reasonable request but using passwords on command line arguments is
really insecure anyway — you still get to see them through /proc, pargs,
process explorer, etc.
jenkins-infra-bot commentedon Oct 15, 2007
Raw content of original comment:
Oh I know, but it's better than nothing for those cases where you have to pass
the password over the command line
jenkins-infra-bot commentedon Oct 15, 2007
Raw content of original comment:
/proc etc. are visible only to people logged in on the same machine (with
appropriate permissions). Quite different from a build log exposed via the web.
jenkins-infra-bot commentedon Oct 15, 2007
Raw content of original comment:
Anyway, agreed that this is a better than nothing feature.
jenkins-infra-bot commentedon Oct 16, 2007
Raw content of original comment:
I have added one approach for the necessary methods to Launcher.launch, added
javadoc warning that these methods only help with the build log, and updated the
change log to reflect this.
Target 1.147
jenkins-infra-bot commentedon Oct 23, 2007
Raw content of original comment:
closing this issue