From: wnoise@ugcs.caltech.edu (Aaron Denney)
To: mlist-linux-kernel@nntp-server.caltech.edu
Subject: Re: [OFFTOPIC] Secure network fileserving Linux <-> Linux
Date: 7 Sep 2001 15:41:40 GMT [thread overview]
Message-ID: <slrn9phqlj.69t.wnoise@barter.ugcs.caltech.edu> (raw)
In-Reply-To: <linux.kernel.20010907025336.D7329@kushida.degree2.com>
Jamie Lokier <lk@tantalophile.demon.co.uk> wrote:
> Jesse Pollard wrote:
> > > Kerberos won't help either - The only parts of NFS that were kerberized
> > > was the initial mount. Everything else uses filehandles/UDP. Encryption
> > > doesn't help either - slows the entire network down too much.
> >
> > I disagree! First of all you can always use NFS over TCP, so much for
> > "every thing else uses filehandles/UDP". (No that this improves security,
> > but it can improve reliability!)
>
> It can improve security if you use NFS over TCP over SSL...
>
> That may be easier to configure than IPSec in some environments.
take a look at sfs: http://www.fs.net/
--
Aaron Denney
-><-
next parent reply other threads:[~2001-09-07 16:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <linux.kernel.20010907025336.D7329@kushida.degree2.com>
2001-09-07 15:41 ` Aaron Denney [this message]
2001-09-07 15:34 [OFFTOPIC] Secure network fileserving Linux <-> Linux Jesse Pollard
2001-09-07 15:58 ` Jamie Lokier
-- strict thread matches above, loose matches on Subject: below --
2001-09-06 12:46 Jesse Pollard
2001-09-07 1:53 ` Jamie Lokier
2001-09-06 12:28 Jesse Pollard
2001-09-06 16:41 ` Mike Fedyk
2001-09-05 19:13 Joseph Mathewson
2001-09-05 19:30 ` Fred
2001-09-05 20:17 ` Frank Schneider
2001-09-05 22:12 ` Jesse Pollard
2001-09-05 22:54 ` Dax Kelson
2001-09-06 1:17 ` John Jasen
2001-09-06 1:54 ` Kain
2001-09-06 3:37 ` Bernd Eckenfels
2001-09-06 12:39 ` Jesse Pollard
2001-09-06 9:20 ` Dominik Kubla
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=slrn9phqlj.69t.wnoise@barter.ugcs.caltech.edu \
--to=wnoise@ugcs.caltech.edu \
--cc=mlist-linux-kernel@nntp-server.caltech.edu \
/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