linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Paul Jakma <paulj@alphyra.ie>
Cc: Dax Kelson <Dax.Kelson@gurulabs.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	NFS maillist <nfs@lists.sourceforge.net>
Subject: Re: [PATCH] Secure user authentication for NFS using RPCSEC_GSS [0/6]
Date: Mon, 13 Jan 2003 13:09:21 +0100	[thread overview]
Message-ID: <15906.44145.47417.934888@charged.uio.no> (raw)
In-Reply-To: <Pine.LNX.4.44.0301130745510.26185-100000@dunlop.admin.ie.alphyra.com>

>>>>> " " == Paul Jakma <paulj@alphyra.ie> writes:

     > On 12 Jan 2003, Dax Kelson wrote:
    >> Standard NFS security/authentication sucks rocks. Without this
    >> NFS home directory servers are just waiting to be ransacked by
    >> a rouge (or compromised) root user on a client machine.

     > AIUI, A root user still can. The users krbv5 credentials will
     > generally have been cached to storage. (though i suppose one
     > could mount that storage via NFS and use root_squash, but
     > that's little protection.).

Once the root account has been compromised, it is 'Game Over' no
matter what you do. Kerberos or no Kerberos, the simplest way to steal
your identity is simply for the attacker to listen in on your tty
while you are typing your password.

The RPCSEC_GSS security model is not meant to protect you against root
monitoring. It is meant to prevent some third party (on another
machine for instance) from spoofing RPC requests in you name (==
strong authentication), intercepting valid RPC requests and modifying
the payload (== cryptographic data integrity checking), or listening
in on the client/server communication (== data privacy).

Cheers,
  Trond

  reply	other threads:[~2003-01-13 12:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-13  0:12 [PATCH] Secure user authentication for NFS using RPCSEC_GSS [0/6] Trond Myklebust
2003-01-13  2:19 ` Jeff Garzik
2003-01-13  2:20   ` Jeff Garzik
2003-01-13  7:50     ` Trond Myklebust
     [not found]       ` <Pine.LNX.4.44.0301131556030.1095-100000@penguin.transmeta.com>
2003-01-14 15:24         ` [PATCH] Fix RPC client warning in 2.5.58 Trond Myklebust
2003-01-13  5:56 ` [PATCH] Secure user authentication for NFS using RPCSEC_GSS [0/6] Dax Kelson
2003-01-13  7:49   ` Paul Jakma
2003-01-13 12:09     ` Trond Myklebust [this message]
2003-01-13 18:06     ` Dax Kelson

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=15906.44145.47417.934888@charged.uio.no \
    --to=trond.myklebust@fys.uio.no \
    --cc=Dax.Kelson@gurulabs.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nfs@lists.sourceforge.net \
    --cc=paulj@alphyra.ie \
    /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).