From mboxrd@z Thu Jan 1 00:00:00 1970 From: erik quanstrom Date: Wed, 14 Mar 2012 14:32:04 -0400 To: blstuart@bellsouth.net, 9fans@9fans.net Message-ID: In-Reply-To: <1331748150.98625.YahooMailClassic@web83911.mail.sp1.yahoo.com> References: <1331748150.98625.YahooMailClassic@web83911.mail.sp1.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: Re: [9fans] GSoC application & ideas page Topicbox-Message-UUID: 69510632-ead7-11e9-9d60-3106f5b1d025 On Wed Mar 14 14:03:34 EDT 2012, blstuart@bellsouth.net wrote: > > >> I'd suggest to complete native SSH2 implementation. > > >=20 > > > ... > >=20 > > Let's not take this one completely off the table yet.=C2=A0 SSHv2 > > would be extremely useful in helping open up communication > > with external systems again. >=20 > As Erik said, there is a substantial effort here, probably > more than we could expect of a student during a summer. > However, I can now say that the effort has been made, and > something more of an announcement will be forthcoming. > It'll probably be at least a few days, but a native SSHv2 > implementation does exist. >=20 > >=C2=A0 I use to find sshnet extremely > > viable in a mixed network where now I'm just using sshv2 to > > tunnel in overly complicated startup scripts. >=20 > There's not a direct replacement for sshnet per se in this > implementation, but here ssh becomes a protocol sitting in > /net.=C2=A0 So it should be pretty easy to tunnel just about > anything, and I suspect that the changes needed to sshnet > would be relatively minor and would cut out all the SSH > protocol bits. boo-ya! - erik