Community
Participate
Working Groups
As far as I understood ssh2 is not supported in eclipse (for cvs access). I just found this link http://www.jcraft.com/jsch/ which has implemented that. Hope this helps ;)
Great, thanks for the pointer! A few notes: 1. You can do ssh2 at present if you use ext and an external ssh2 client (but its not as nice a solution as the integrated extssh 1 we have now) 2. A quick look at jcraft indicates its GNU LGPL :( 3. It requires jdk 1.4.0 :( So we may be able to use, but its not a slam dunk.
look here:
oops - presses commit too early - maybe you can conveince http://www.appgate.com/mindterm/ to contribute the code - either in source or binary form
Hi, I'm an author of jsch(http://www.jcraft.com/jsch/) and I'm interested in a comment from Kevin McGuire. I'm not familiar with the license of Eclipse, but is there a problem in integrating GNU LGPL program? I had planed to contribute CVS-SSH2 plug-in by using my stuff, but is there a possibility that my contribution may be rejected?
btw I understood jsch has a bsd style license now..
*** Bug 26937 has been marked as a duplicate of this bug. ***
*** Bug 264 has been marked as a duplicate of this bug. ***
*** Bug 37476 has been marked as a duplicate of this bug. ***
It there any luck to integrate jcraft's ssh2 plugin into Eclipse 3.0? It is working for 2.x, but not in 3.0
I'm using it with Eclipse 3.0M2 and it's working great. No problems yet.
Sven, are you talking about standart Eclipse extssh protocol or about extssh2 added by the jcraft's plugin?
jcraft's plugin is working in 3.0M2 for me fine too
Will the standard eclipse extssh protocol be supporting the ssh2 protocol (for cvs repository access) in the future. Since we are being forced not to use the ssh1 protocol ?
The reason for the comment above is because of a comment made on defect 26937 by Boris Shingarov "Support for this will be in the SSH2 plugin that is currenty being dveloped." Just wondering about the status of it
Kevin McGuire 2002-10-23 09:51 ------- > 1. You can do ssh2 at present if you use ext and an external ssh2 > client (but its not as nice a solution as the integrated extssh 1 we > have now) ... a major understatement. One really must configure ssh-agent to be at all productive "[using] ext and an external ssh2 client," and this is non-trivial. > 2. A quick look at jcraft indicates its GNU LGPL :( Currently (07:58:52 PM EST 12 Oct 03) http://www.jcraft.com/jsch/ > JSch is licensed under BSD style license. http://www.jcraft.com/jsch/LICENSE.txt > JSch 0.0.* was released under the GNU LGPL license. Later, we have > switched over to a BSD-style license. > -------------------------------------------------------------------- > Copyright (c) 2002,2003 ymnk, JCraft,Inc. All rights reserved. > Redistribution and use in source and binary forms, with or without > modification, are permitted provided that the following conditions > are met: > 1. Redistributions of source code must retain the above copyright > notice, this list of conditions and the following disclaimer. > 2. Redistributions in binary form must reproduce the above copyright > notice, this list of conditions and the following disclaimer in > the documentation and/or other materials provided with the > distribution. > 3. The names of the authors may not be used to endorse or promote > products derived from this software without specific prior > written permission. > THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED > WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF > MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. > IN NO EVENT SHALL JCRAFT, INC. OR ANY CONTRIBUTORS TO THIS SOFTWARE > BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, > OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT > OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR > BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF > LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING > NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS > SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. IANAL but I have spent quite a while in <an unnameable IBM open-source-release-approval process>, and the above looks pretty permissive to me. Better yet: http://www.jcraft.com/eclipse-cvsssh2/ > This plug-in is licensed under the terms and conditions of CPL 1.0. i.e. same as Eclipse. Kevin McGuire 2002-10-23 09:51 ------- > 3. It requires jdk 1.4.0 :( Not quite: http://www.jcraft.com/jsch/ > JSch is in pure Java, but it depends on JavaTM Cryptography > Extension (JCE). Jsch is know [sic] to work with: > * J2SE 1.4.0 or later (no additional libraries required). > * J2SE 1.3 and Sun's JCE reference implementation that can be > obtained at http://java.sun.com/products/jce/. plus, now that 3.0-M4 supports 1.4.x, this is not a problem, n'c'est pas?
Hi, I'm author of jsch. |> JSch is in pure Java, but it depends on JavaTM Cryptography |> Extension (JCE). Jsch is know [sic] to work with: |> * J2SE 1.4.0 or later (no additional libraries required). |> * J2SE 1.3 and Sun's JCE reference implementation that can be |> obtained at http://java.sun.com/products/jce/. |plus, now that 3.0-M4 supports 1.4.x, this is not a problem, n'c'est |pas? FYI, recently, I have succeeded in running jsch on JDK 1.1.* thanks to Bouncy Castle Crypto APIs. That means jsch can run on J2SE 1.3 without JCE. I have received many requests from enterprise users, who are using WASD and can not change their platform from J2SE 1.3 to 1.4 and have troubles in using JCE. That work is my solution for them. I have a question that how about the compatibility between the License of BouncyCastle API and CPL? Frankly to say, I'm not so interested in running Eclipse on J2SE 1.3 platform, so I have hesitated to release it, however I may release it if it is worth existing.
We are integrating JCraft's ssh2 plugin into Eclipse and should have a beta ready for M6. Our plans are to: - create a SSH2 connection method for 2.1.* that can be downloaded from the CVS Eclipse website. We don't plan on supporting users running on J2SE 1.3. - create a SSH2 connection method for 3.* users that will effectively replace the current 'extssh' method. We would like to thank Atsuhiko Yamanaka for contributing this code and agreeing to be the committer for this plug-in.
SSH2 has been integrated in M6. In order to keep M6 as stable as possible we will keep it turned off by default. Our plan is to enable by default for the first integration build after M6. To enable, goto the following preference page: Team > CVS > SSH2 Connection Method. All connection types 'extssh' will use SSH2 from that point on. The plug-in supports the following features: * This plug-in requires J2SE 1.4 * SSH2 protocol support * This plug-in supports password, public-key and keyboard-interactive authentications. * This plug-in supports HTTP,SOCKS5 proxies to get SSH2 access beyond the firewall. * This plug-in has solved the problem 'Eclipse opens SSH connection for every tiny CVS operation' by re-using server connections. * Supports DSA, RSA key generation Again, thanks to Atsuhiko Yamanaka or Jcraft.com for contributing the code and helping me integrate this into Eclipse!!
*** Bug 49967 has been marked as a duplicate of this bug. ***
Thanks for your work Atsuhiko Yamanaka.
