Adding SSHH, SSH2,telnet functionality

Okay, I began porting an application to work on JNode. The application it a terminal that allows SSH, SSH2, and telnet connections.

Ok, so after reviewing some of the packages JNode uses, I found some of them that I was porting. So now begins the task of just making clients.

**This post was edited on 2/10/2007

I'd like to test them, is

Submitted by pablod on Sat, 06/16/2007 - 02:28.

I'd like to test them, is it available...?

Changed Classes because of porting

Submitted by The Captain on Wed, 02/07/2007 - 20:49.

java.lang.Math - add two methods that deal with BigIntergers for ciper generation
javax.net.SocketFacotry - added 4 methods to deal with SSH, will edit to transfer to another factory later

classes from GNU Classpath

Submitted by Fabien D on Fri, 02/09/2007 - 12:27.

That's classes from GNU Classpath implementation. You shouldn't modify them.
Is that because lack of implementation from GNU Classpath ? If so, they you should consider giving your code to GNU Classpath (licensed under GPL with Classpath exception).

Fabien

my blog (in english and french)

I'm just using them for

Submitted by The Captain on Fri, 02/09/2007 - 19:51.

I'm just using them for simplifying testing.
They'll be seperate of the classpath once testing is finished.

I agree with Fabien

Submitted by Stephen Crawley on Sat, 02/10/2007 - 18:57.

If you are adding implementations for standard methods that are not implemented in the Classpath versions of classes, they should be contributed back to the Claspath codebase. This will allow other Classpath-based projects get the benefit of your work. This is the way open source is supposed to work.

On the other hand, if you are adding new non-standard methods to standard classes, DON'T DO IT! It will will cause problems down the track for people porting Java code developed on JNode to other Java platforms.