From: lucio@proxima.alt.za
To: 9fans@9fans.net
Subject: Re: [9fans] exportfs security question
Date: Mon, 13 Apr 2009 06:45:33 +0200 [thread overview]
Message-ID: <90a0611832e4e051693aae1ddd9742d9@proxima.alt.za> (raw)
In-Reply-To: <dd6fe68a0904111624p1ae8acd6s6cf94263b105fcd5@mail.gmail.com>
> all the auth protocols are due for a rework,
> but honestly i don't think anyone cares
> enough to see it through, myself included.
Posting some guidelines, not least _known_ good reasons to do it, may
encourage someone to go ahead. In fact, it would also make for useful
suggestions for GSoC projects.
++L
prev parent reply other threads:[~2009-04-13 4:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-10 8:41 Nathaniel W Filardo
2009-04-10 10:25 ` Steve Simon
2009-04-10 15:18 ` Nathaniel W Filardo
2009-04-10 11:48 ` erik quanstrom
2009-04-10 12:08 ` Mechiel Lukkien
2009-04-10 15:17 ` Nathaniel W Filardo
2009-04-11 23:24 ` Russ Cox
2009-04-13 4:45 ` lucio [this message]
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=90a0611832e4e051693aae1ddd9742d9@proxima.alt.za \
--to=lucio@proxima.alt.za \
--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).