Thomas Wolf f67af4e16b Work around a Jsch bug: ensure the user name is set from URI ... JSch unconditionally overrides the user name given in the connection URI by the one found in ~/.ssh/config (if that does specify one for the used host). If the SSH config file has a different user name, we'll end up using the wrong name, which typically results in an authentication failure or in Eclipse/EGit asking for a password for the wrong user. Unfortunately there is no way to prevent or circumvent this Jsch behavior up front; it occurs already in the Session constructor at com.jcraft.jsch.Session() and the Session.applyConfig() method. And while there is a Session.setUserName() that would enable us to correct this, that latter method has package visibility only. So resort to reflection to invoke that setUserName() method to ensure that Jsch uses the user name from the URI, if there is one. Bug: 526778 Change-Id: Ia327099b5210a037380b2750a7fd76ff25c41a5a Signed-off-by: Thomas Wolf <thomas.wolf@paranor.ch>		2017-11-10 10:16:58 +01:00
..
gitrepo/internal	ManifestParser: Throw exception if remote does not have fetch attribute	2017-04-10 15:08:32 +02:00
internal	Work around a Jsch bug: ensure the user name is set from URI	2017-11-10 10:16:58 +01:00
util/sha1	Move SHA1 compress/recompress files to resource folder	2017-03-18 16:46:58 +01:00