Matthias Wiedemann
Matthias Wiedemann
never heard of `ssh-rp` Key type. Maybe a typo in your or the servers ssh config?
We have that Unit-Test in https://github.com/mwiede/jsch/blob/966e7fd55e443939b80134f17cb117b3ca642561/src/test/java/com/jcraft/jsch/KeyPairTest.java#L125-L139 Maybe you take that code and try to load your keys to find the issue
not here, but there https://github.com/mwiede/jsch
probably you should switch to https://github.com/mwiede/jsch
Please use one of the loggers to show the output of the logs. My first guess is that you use ssh-rsa which is deactivated by default in the fork.
The fork includes a few built-in loggers for various frameworks, see JplLogger, JulLogger, Log4j2Logger & Slf4jLogger. Any of the above loggers can be enabled with the JSch.setLogger(), JSch.setInstanceLogger() or Session.setLogger()...
are you sure, that the issue comes from switching the library? When looking at google results, it seems, it's a popular issue which is caused by timeout and server workload....
If sha2 is not activated on the server, it won't work. You could check server config by sshd -T
Is included already see #65
didnt you want to use pageant (on windows)? Then it would have been ``` IdentityRepository irepo = new AgentIdentityRepository(new PageantConnector()); jsch.setIdentityRepository(irepo); ```