Markus Hoffrogge opened SCM-1028 and commented
Issue(s):
- {}JGit provider{}: If the git password contains special characters which are differently encoded by the
URI class than {}by URLEncode.encode{}, then the password masking does not become effective and the password is logged in clear URI encoded format by the jgit provider.
- {}Gitexe remoteinfo{}: In case ls-remote is failing, then a
ScmException is being thrown with the fetch URL passed as error message containing the URI encoded clear password.
Root cause(s):
- The URL encoding used for the credentials within fetch and push URL differs from the encoding being used for masking the password at JGitUtils.prepareSession(...)
- Password is not masked for the exception message passed to the ScmException used at GitRemoteInfoCommand.executeRemoteInfoCommand(...)
Solution:
PR #237
Affects: 2.1.0
Remote Links:
Markus Hoffrogge opened SCM-1028 and commented
Issue(s):
URI classthan{}by URLEncode.encode{}, then the password masking does not become effective and the password is logged in clear URI encoded format by the jgit provider.ScmExceptionis being thrown with the fetch URL passed as error message containing the URI encoded clear password.Root cause(s):
Solution:
PR #237
Affects: 2.1.0
Remote Links: