You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "gurka (via GitHub)" <gi...@apache.org> on 2023/09/28 10:29:54 UTC

[GitHub] [mina-sshd] gurka commented on issue #309: Allow for the use of HTTP or SOCKS proxies

gurka commented on issue #309:
URL: https://github.com/apache/mina-sshd/issues/309#issuecomment-1738887229

   Hi @david0 , sorry to ping you here, but I just wanted to ask if you (or anyone else here) know if public key identities has to be added in another way after switching to JGitSshClient? It successfully connects via SOCKS, but during authentication it says that no public keys are available. What is also strange is that it tries to use the DefaultClientIdentityLoader even though I have set a custom one.
   
   This all worked OK before I added JGitSshClient. I guess this is related to this comment in JGitSshClient.java
   > It creates specialized JGitClientSessions that know about the HostConfigEntry they were created for, and it loads all KeyPair identities lazily.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@mina.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@mina.apache.org
For additional commands, e-mail: dev-help@mina.apache.org