From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <1331748150.98625.YahooMailClassic@web83911.mail.sp1.yahoo.com> Date: Wed, 14 Mar 2012 11:02:30 -0700 From: "Brian L. Stuart" To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [9fans] GSoC application & ideas page Topicbox-Message-UUID: 694af760-ead7-11e9-9d60-3106f5b1d025 > >> I'd suggest to complete native SSH2 implementation.=0A> > =0A> > ...= =0A> =0A> Let's not take this one completely off the table yet.=A0 SSHv2=0A= > would be extremely useful in helping open up communication=0A> with exter= nal systems again.=0A=0AAs Erik said, there is a substantial effort here, p= robably=0Amore than we could expect of a student during a summer.=0AHowever= , I can now say that the effort has been made, and=0Asomething more of an a= nnouncement will be forthcoming.=0AIt'll probably be at least a few days, b= ut a native SSHv2=0Aimplementation does exist.=0A=0A>=A0 I use to find sshn= et extremely=0A> viable in a mixed network where now I'm just using sshv2 t= o=0A> tunnel in overly complicated startup scripts.=0A=0AThere's not a dire= ct replacement for sshnet per se in this=0Aimplementation, but here ssh bec= omes a protocol sitting in=0A/net.=A0 So it should be pretty easy to tunnel= just about=0Aanything, and I suspect that the changes needed to sshnet=0Aw= ould be relatively minor and would cut out all the SSH=0Aprotocol bits.=0A= =0ABLS=0A