From: Jamie Lokier <lk@tantalophile.demon.co.uk>
To: Jesse Pollard <pollard@tomcat.admin.navo.hpc.mil>
Cc: kubla@sciobyte.de, joe@mathewson.co.uk, linux-kernel@vger.kernel.org
Subject: Re: [OFFTOPIC] Secure network fileserving Linux <-> Linux
Date: Fri, 7 Sep 2001 02:53:36 +0100 [thread overview]
Message-ID: <20010907025336.D7329@kushida.degree2.com> (raw)
In-Reply-To: <200109061246.HAA61789@tomcat.admin.navo.hpc.mil>
In-Reply-To: <200109061246.HAA61789@tomcat.admin.navo.hpc.mil>; from pollard@tomcat.admin.navo.hpc.mil on Thu, Sep 06, 2001 at 07:46:37AM -0500
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.
-- Jamie
next prev parent reply other threads:[~2001-09-07 13:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-06 12:46 [OFFTOPIC] Secure network fileserving Linux <-> Linux Jesse Pollard
2001-09-07 1:53 ` Jamie Lokier [this message]
[not found] <linux.kernel.20010907025336.D7329@kushida.degree2.com>
2001-09-07 15:41 ` Aaron Denney
-- strict thread matches above, loose matches on Subject: below --
2001-09-07 15:34 Jesse Pollard
2001-09-07 15:58 ` 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=20010907025336.D7329@kushida.degree2.com \
--to=lk@tantalophile.demon.co.uk \
--cc=joe@mathewson.co.uk \
--cc=kubla@sciobyte.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pollard@tomcat.admin.navo.hpc.mil \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.