We don't have many options. I'd say, first of all we should open a PR
with
the fix and ask for a release, even if we know it is unlikely to be
consdered.
See https://github.com/ymnk/jsch-agent-proxy/issues/28 ;-) Please add
any +1s there, although I fear it's unlikely to help.
If we're going to consider going down the road of releasing some of this
ourselves and/or incorporating the relevant code (just a few classes,
but we'd need to look at licensing), we might consider reverting
JCLOUDS-1051 [1]. We would probably just need to change the
jsch-agent-proxy-sshj POM in the same way as in this commit [2].
Regards
ap
[1] https://issues.apache.org/jira/browse/JCLOUDS-1051
[2]
https://github.com/ymnk/jsch-agent-proxy/commit/2d59e3b93dc400f2145b787d667444d8fe3201e3
