From: Jeff Sickel <jas@corpus-callosum.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] GSoC application & ideas page
Date: Wed, 14 Mar 2012 00:40:57 -0500 [thread overview]
Message-ID: <9931E00A-AE5D-4528-B072-AADB5EC00182@corpus-callosum.com> (raw)
In-Reply-To: <A24F809C-01B3-4EDD-A3B0-DC651E053281@9srv.net>
On Mar 13, 2012, at 11:42 PM, Anthony Sorace wrote:
>> I'd suggest to complete native SSH2 implementation.
>
> This has obvious utility, but I'm hesitant to add it without a
> mentor who can vouch for its suitability for a summer-sized
> student project, and who'd be willing to mentor a good
> proposal for it. To me, it seems larger than that, but I'd be
> happy to be wrong. Any takers?
Let's not take this one completely off the table yet. SSHv2
would be extremely useful in helping open up communication
with external systems again. 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.
If someone is interested, with a predisposition towards
security issues, including a track record of tackling such
a task, I'd say we encourage it. Getting us one step closer
to dealing with the default toolchain for many systems would
help for any future projects.
-jas
next prev parent reply other threads:[~2012-03-14 5:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-12 16:46 Anthony Sorace
2012-03-13 7:05 ` Peter A. Cejchan
2012-03-13 11:29 ` Yaroslav
2012-03-14 4:42 ` Anthony Sorace
2012-03-14 5:40 ` Jeff Sickel [this message]
2012-03-14 13:15 ` erik quanstrom
[not found] ` <CAG3N4d8ZQB7_8dsH8NfxB5Tj2ZtaGVfH7ZvuzWjYMT1X1jW6Xg@mail.gmail.c>
2012-03-13 12:51 ` erik quanstrom
2012-03-13 13:28 ` erik quanstrom
2012-03-13 20:18 ` John Floren
2012-03-14 7:11 ` Peter A. Cejchan
[not found] ` <CAL4LZyi-Tv-5C-QAKA+wOdcciUepZrw=OCEjhdLSPG=rg3n6Mg@mail.gmail.c>
2012-03-13 20:24 ` erik quanstrom
2012-03-14 18:02 Brian L. Stuart
2012-03-14 18:32 ` erik quanstrom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9931E00A-AE5D-4528-B072-AADB5EC00182@corpus-callosum.com \
--to=jas@corpus-callosum.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).