Howdy --
Any chance of getting code review on this? I'm in the process of submitting
a dependent patch to IntelliJ IDEA (
https://github.com/JetBrains/intellij-community/pull/78), and would very
much prefer not to be creating a fork / causing a divergence from upstream.
On Wed, May 22, 2013 at 1
Howdy --
I've attached a patch to TMateSoft's fork of Trilead SSH2 to
http://issues.tmatesoft.com/issue/SVNKIT-178, and links to github branches
with appropriate changes to jsch-agent-proxy (
https://github.com/charles-dyfis-net/jsch-agent-proxy/tree/trilead-ssh2-support)
and SVNKit (https://githu
Thank you for the response.
I've decided, rather than switching back to JSch, to add ssh-agent support
to Trilead SSH2. I have an experimental branch of Orion (based on
https://orion-ssh2.svn.sourceforge.net/svnroot/orion-ssh2) patched
appropriately (the Orion project claims to be the succ
> I'm interested in adding SSH agent support to SVNKit to allow a
> (potentially remote/forwarded) agent to perform authentication on behalf of
> the library.
>
> Upstream support for this is available as an easy-to-integrate 3rd-party
> library for JSch; however, it appea
Hello Charles,
> I'm interested in adding SSH agent support to SVNKit to allow a (potentially
> remote/forwarded) agent to perform authentication on behalf of the library.
That sounds great!
> What's the history behind this? How much has the interface changed since the
> J
Howdy --
I'm interested in adding SSH agent support to SVNKit to allow a
(potentially remote/forwarded) agent to perform authentication on behalf of
the library.
Upstream support for this is available as an easy-to-integrate 3rd-party
library for JSch; however, it appears that SVNKi