On 11/09/2009 08:22 PM, Atsuhiko Yamanaka wrote: > Hi, > > +-From: Paul Michael Reilly<p...@pajato.com> -- > |_Date: Mon, 09 Nov 2009 06:20:35 -0500 _______ > | > |So my first question is: what is the plan for dealing with this lack of > |documentation, particularly for Javadoc? > > You are welcome to improve documentations. > There is a wiki site http://wiki.jsch.org/ , > which waits for your contributions.
I believe you are the person who deserves much, if not all, of the credit for JSch. This is a class library for which I am very grateful as the SSH library I was using (trilead) has gone closed source. So, many kudos from me to you. However, I must take JSch to task for the sorry state of the internal code comments, especially Javadoc. Are you open to accepting source code changes that provide substantial Javadoc additions and some minimal code refactoring? If so then I will gladly either send patches and at some point lobby for commit access to your source repository. > > |My second desire is to understand the approach one should use to > |establish a session without the need to provide a password, i.e. the > |public key has already been installed to the SSH server. I tried > |grokking the examples but I found them less than helpful. Perhaps > |someone has done this? > > Please check if the private key is in OpenSSH format, > and then file access permissions of remote files; > ~/.ssh and ~/.ssh/authorized_keys must be in go-rwx . Keith Alan Richardson provided a very nice answer in this thread and I would implore JSch to adopt his style for the code examples. I was able to discern from his code the answer that I needed almost immediately where the original examples are just not sufficiently polished to easily learn the important concepts. Please do not take offense. I am willing to help make this library become more polished if my offer to help is accepted. I have less desire to fill the gap in the wiki as I strongly believe it is the code base that many experienced programmers like myself will use to deal with bugs and to attempt to understand the underlying intent and design, and thus the use of the library, much in the same way we go to the Java API Javadoc to find out how to correctly use those classes. In any case I will continue to use and sing the praises of JSch and be grateful that you undertook to produce it. -pmr ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ JSch-users mailing list JSch-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jsch-users