Currently ssh client parses per default the $HOME/.ssh/config client config. This can be turned off in code with a HostConfigEntryResolver returning null.
I believe parsing the config by default is beyond the scope of an ssh client. This should be off by default. A Java client library is not the Unix ssh command, so it should not automatically parse the config. Parsing the config can have unexpected side effects: My Windows %UserProfile%\.ssh\config is for MSYS2 Unix environment, it contains id pathes in Cygwin syntax and in quotes. Both break the 2.7.0 ssh parser. This can be fixed with a HostConfigEntryResolver. But this should not be necessary in the first place. Config parsing should only be activated with a System property or a client Builder option. Thanks, Juergen --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@mina.apache.org For additional commands, e-mail: users-h...@mina.apache.org
