Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
Received-SPF: pass (athena.apache.org: domain of vinod.ofgovind@gmail.com
 designates 74.125.92.147 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=gS7nFFLCxNqWhLHiND0kOeH2Xr827IInCOSte6OQ9hq/r9a4DyHB8IWtrrJ9nE+oMx
         n90zDKWb9ppBD3FsFjB6SCOMDLjWX4NEQ8ig2iZ8m9cQ/5U1q9CIvxA2HJlMvR0SUBMj
         lM1T0UN20XrJaKktkIM+6IFKFil0pTOGKluoQ=
MIME-Version: 1.0
In-Reply-To: <b23ecedc0904110817m7ee67c0fs1abfafcdfba32d56@mail.gmail.com>
References: <824aa8970904080339i7686a8e0nf96bc87d1e7d84f9@mail.gmail.com>
	 <b23ecedc0904110817m7ee67c0fs1abfafcdfba32d56@mail.gmail.com>
Date: Sun, 12 Apr 2009 02:12:49 +0530
Message-ID: <824aa8970904111342j5d32d3d8mccc8aecfce19e794@mail.gmail.com>
Subject: Re: SSH Implementation - IDEA and seeking Suggestions.
From: Vinod Kumar Badhavat <vinod.ofgovind@gmail.com>
To: Commons Developers List <dev@commons.apache.org>
Content-Type: multipart/alternative; boundary=0016e646544e3f50c904674d860f

--0016e646544e3f50c904674d860f
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Hi Guillaume Nodet

Thank you for your information. I applied to Apache as a part of Google
Summer of Code(GSoC), so I think, I should stick to the proposal I made in
the application and implement SSH as a part of commons-net. I would like to
use SSHD's key and algorithm negotiation. I'm planning to use java
cryptography directly. If this is not so useful, then i may turn to SSHD's
crypto.

can i use mina's mailing list to discuss about SSH Implementation?

--- Vinod.

On Sat, Apr 11, 2009 at 8:47 PM, Guillaume Nodet <gnodet@gmail.com> wrote:

> In case you haven't followed the earlier discussion, you may want to
> have a look at the Apache SSHD project, which implements an SSH server
> and some parts of the client.  The client is far from complete, so it
> may be a good idea to join our forces:
>   http://svn.apache.org/repos/asf/mina/sshd/trunk/
>
> Currently, the client api is asynchronous, but it would make sense to
> add a synchronous api for ease of use.
> In all cases, feel free to reuse any code from this project, as most
> of the crypto stuff / kex negociation and other algorithms have
> already been implemented, as there's really no need to duplicate the
> work.
>
> 2009/4/8 Vinod Kumar Badhavat <vinod.ofgovind@gmail.com>:
> dev-subscribe@mina.apache.org
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
> ------------------------
> Open Source SOA
> http://fusesource.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>

--0016e646544e3f50c904674d860f--