From: "Jorge R . Csapo" <jorge@completo.com.br>
To: linux-admin@vger.kernel.org
Subject: NIS and NFS
Date: Tue, 25 Mar 2003 14:41:05 -0200 [thread overview]
Message-ID: <20030325144105.B6601@completo.com.br> (raw)
Hi all, I've been wrecking my brains over this one but I'm threading water:
I have a Linux-only network with one server and a number of stations. The
server's /home directory is exported and mounted by the stations via NFS. The
server also serves NIS and the setup lets users log onto any one of the
stations and have the same /home/~user everywhere.
My problem is that every user is 'root' at his/her own station. Of course NFS
has been configured not to grant access to remote root users, but there's
nothing to prevent users from 'becoming' someone else with su and then the
NFS/NIS authentication scheme falls flat on its face.
For instance:
. User 'jdoe' logs onto his own station. He's authenticated via NIS and mounts
/home from the server.
. jdoe then runs 'su' and becomes root.
. root runs 'su - jblow' and becomes jblow.
. jblow cds to /home/jblow...
After going through man docs, howtos and google entries for NIS, NFS and su and
drawing a blank, I'd appreciate any and all insights you people may have on
the subject.
TIA,
--
Jorge R. Csapo
--------------------------------------------------
/"\
\ / CAMPANHA DA FITA ASCII - CONTRA MAIL HTML
X ASCII RIBBON CAMPAIGN - AGAINST HTML MAIL
/ \
--------------------------------------------------
http://www.completo.com.br/~jorge
===========================================
With a PC, I always felt limited
by the software available.
On Unix, I am limited only by my knowledge.
--Peter J. Schoenster
next reply other threads:[~2003-03-25 16:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-25 16:41 Jorge R . Csapo [this message]
2003-03-25 20:28 ` NIS and NFS Michael Salmon
2003-03-26 12:48 ` Jorge R . Csapo
-- strict thread matches above, loose matches on Subject: below --
2003-03-25 20:28 Michael Salmon
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=20030325144105.B6601@completo.com.br \
--to=jorge@completo.com.br \
--cc=linux-admin@vger.kernel.org \
/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).