|
»
»
»
« Return to Thread: ganymed|trilead ssh2 status
Re: ganymed|trilead ssh2 status
by Alexander Kitaev-3
::
Rate this Message:
Hello,
We were not aware that Trilead SSH library is no longer supported.
In the early time of SVNKit development JSCH were used, but
unfortunately, at least that time it appeared to be very unstable and
code quality of it was very poor, plus basically no real bugfixing took
place.
That time JSCH worked well only in a fixed number of a very simple use
cases (those of CVS Eclipse plugin) and didn't allow to create reliable
code that will use all SSH features (like keeping one SSH connection
with multiple channels being used from multiple threads and creating
pool of them; or checking private key integrity with utility methods; or
"pinging" existing channel or session to make sure it is still alive).
JSCH basically didn't work when making anything more than just
establishing single connection. Trilead also has very clear source code
that is easy to debug in case there are any problems (comparing to the
old version of JSCH).
So we choose Ganymede library and never regret - it also had excellent
support through all the time we're using it.
On the other side you're right - SVNKit allows to plug in different
implementation for creating SSH (or any other) 'tunnel'. I think for the
next version of SVNKit we'll add option JSCH svn+ssh implementation and
in case it will work well we'll make it default.
Also, in the meantime we will put Trilead SSH library source code into
our repository (it is also distributed under BSD license) so it will
remain available for the community and we still will be able to make
minor bugfixes in it when necessary.
Alexander Kitaev,
TMate Software,
http://svnkit.com/ - Java [Sub]Versioning Library!
Dale Anson wrote:
> The jsch library would be a good choice. It's been around for quite a
> while and is actively maintained. It has a BSD-style license so there
> should be no problem license-wise. It looks like the trilead library is
> used in only 3 files in svnkit, so I'm thinking it wouldn't be too hard
> to replace it, but I didn't look deeper to confirm that.
> Dale
>
>
> Robert Marcano wrote:
>> Greetings, just noticed today that trilead-ssh2 is not maintained
>> anymore and points again to the original ganymed-ssh2 page
>>
>> http://www.trilead.com/SSH_Library/
>>
>> and that page points again to the trilead page.
>>
>> I am the packager of svnkit for Fedora and want to ask what can we
>> do about this, ssh is a security technology and is not good to use a
>> library without support
>>
>> today released SVNKit uses trilead version
>>
>> what about using Jsch that is already on Eclipse?
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: svnkit-users-unsubscribe@...
> For additional commands, e-mail: svnkit-users-help@...
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: svnkit-users-unsubscribe@...
For additional commands, e-mail: svnkit-users-help@...
We were not aware that Trilead SSH library is no longer supported.
In the early time of SVNKit development JSCH were used, but
unfortunately, at least that time it appeared to be very unstable and
code quality of it was very poor, plus basically no real bugfixing took
place.
That time JSCH worked well only in a fixed number of a very simple use
cases (those of CVS Eclipse plugin) and didn't allow to create reliable
code that will use all SSH features (like keeping one SSH connection
with multiple channels being used from multiple threads and creating
pool of them; or checking private key integrity with utility methods; or
"pinging" existing channel or session to make sure it is still alive).
JSCH basically didn't work when making anything more than just
establishing single connection. Trilead also has very clear source code
that is easy to debug in case there are any problems (comparing to the
old version of JSCH).
So we choose Ganymede library and never regret - it also had excellent
support through all the time we're using it.
On the other side you're right - SVNKit allows to plug in different
implementation for creating SSH (or any other) 'tunnel'. I think for the
next version of SVNKit we'll add option JSCH svn+ssh implementation and
in case it will work well we'll make it default.
Also, in the meantime we will put Trilead SSH library source code into
our repository (it is also distributed under BSD license) so it will
remain available for the community and we still will be able to make
minor bugfixes in it when necessary.
Alexander Kitaev,
TMate Software,
http://svnkit.com/ - Java [Sub]Versioning Library!
Dale Anson wrote:
> The jsch library would be a good choice. It's been around for quite a
> while and is actively maintained. It has a BSD-style license so there
> should be no problem license-wise. It looks like the trilead library is
> used in only 3 files in svnkit, so I'm thinking it wouldn't be too hard
> to replace it, but I didn't look deeper to confirm that.
> Dale
>
>
> Robert Marcano wrote:
>> Greetings, just noticed today that trilead-ssh2 is not maintained
>> anymore and points again to the original ganymed-ssh2 page
>>
>> http://www.trilead.com/SSH_Library/
>>
>> and that page points again to the trilead page.
>>
>> I am the packager of svnkit for Fedora and want to ask what can we
>> do about this, ssh is a security technology and is not good to use a
>> library without support
>>
>> today released SVNKit uses trilead version
>>
>> what about using Jsch that is already on Eclipse?
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: svnkit-users-unsubscribe@...
> For additional commands, e-mail: svnkit-users-help@...
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: svnkit-users-unsubscribe@...
For additional commands, e-mail: svnkit-users-help@...
« Return to Thread: ganymed|trilead ssh2 status
| Free embeddable forum powered by Nabble | Forum Help |
