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 > JSch implementation was canned? Could I expect to be able to resurrect the > old implementation with a reasonable level of effort? We've switched to trilead from jsch due to a poor quality of the latter, at least at the moment we used it. While jsch worked well in a simple use cases, it failed in more complex ones, like using multiple channels per connection. It might be different now. > JSch implementation was canned? Could I expect to be able to resurrect the > old implementation with a reasonable level of effort? One could implement ISVNConnector interface to use jsch library, then call SVNRepositoryFactoryImpl.setup(connectorFactory) to make SVNKit use new connector for SSH connections. Alexander Kitaev, TMate Software, http://subgit.com/ - Svn to Git Migration! http://svnkit.com/ - Java [Sub]Versioning Library! http://hg4j.com/ - Java Mercurial Library! http://sqljet.com/ - Java SQLite Library! On 21 May 2013 20:06, Charles Duffy <char...@dyfis.net> wrote: > 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 SVNKit has transitioned away from > using JSch as its SSH implementation. > > What's the history behind this? How much has the interface changed since the > JSch implementation was canned? Could I expect to be able to resurrect the > old implementation with a reasonable level of effort?
