From: David Leimbach <leimy2k@gmail.com>
To: Eric Van Hensbergen <ericvh@gmail.com>
Cc: erik quanstrom <quanstro@quanstro.net>,
V9FS Developers <v9fs-developer@lists.sourceforge.net>,
Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Re: [V9fs-developer] playing with Tim's python 9p implementation
Date: Tue, 4 Oct 2005 08:22:46 -0700 [thread overview]
Message-ID: <3e1162e60510040822r7b118fc1rb74cc946cd036127@mail.gmail.com> (raw)
In-Reply-To: <a4e6962a0510040818y50a4fa40r9c277f79e7071657@mail.gmail.com>
> I'd like to get a more-pure Linux auth infrastructure in place -- at
> the very least being able to host auth servers under Linux, either
> using Plan 9 ports or by porting them (IIRC: there were some unix auth
> tools, but maybe I'm just thinking of netkey). There's also the
> option of trying for a Kerberos or SASL auth mechanism for Linux-only
> environments. This stuff just hasn't been a priority for me because
> its not a concern in my environment, but its something we clearly need
> a better story on.
>
Yeah, auth would be cool, but I don't need it for what I'm planning to
do with v9fs either.
Dave
> -eric
>
next prev parent reply other threads:[~2005-10-04 15:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3e1162e60510031714y15fa11b0tf15a3bc314fe26e0@mail.gmail.com>
[not found] ` <20051004120350.44AA61418FF@dexter-peak.quanstro.net>
2005-10-04 14:41 ` David Leimbach
2005-10-04 14:43 ` Eric Van Hensbergen
2005-10-04 14:56 ` Ronald G Minnich
2005-10-04 15:01 ` David Leimbach
2005-10-05 23:26 ` C H Forsyth
[not found] ` <17359dff2944f0b6ab9858ace89d5cac@vitanuova.com>
2005-10-05 23:40 ` David Leimbach
2005-10-04 15:18 ` Eric Van Hensbergen
2005-10-04 15:22 ` David Leimbach [this message]
2005-10-05 4:33 ` Tim Newsham
2005-10-05 4:33 ` Tim Newsham
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=3e1162e60510040822r7b118fc1rb74cc946cd036127@mail.gmail.com \
--to=leimy2k@gmail.com \
--cc=9fans@cse.psu.edu \
--cc=ericvh@gmail.com \
--cc=quanstro@quanstro.net \
--cc=v9fs-developer@lists.sourceforge.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).