Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!husc6!bbn!uwmcsd1!marque!uunet!mcvax!enea!kth!luth!eru.mt.luth.se!sow
From: sow@eru.mt.luth.se (Sven-Ove Westberg)
Newsgroups: comp.unix.wizards
Subject: Re: NFS security
Keywords: NFS, mknod
Message-ID: <1202@luth.luth.se>
Date: 2 Sep 88 14:35:00 GMT
References: <126@leibniz.UUCP> <670028@hpclscu.HP.COM> <1394@basser.oz> <604@sequent.cs.qmc.ac.uk>
Sender: news@sm.luth.se
Reply-To: Sven-Ove Westberg <sow@cad.luth.se>
Organization: University of Lulea, Sweden
Lines: 21
UUCP-Path: {uunet,mcvax}!enea!cad.luth.se!sow

In article <604@sequent.cs.qmc.ac.uk> liam@cs.qmc.ac.uk (William Roberts) writes:
|In article <1394@basser.oz> yar@basser.oz (Ray Loyzaga) writes:
|>
|>Well what happens if on SunOS 3.5 you do as root on your
|>workstation on a remote fs
|>mknod ~mydir/mem c 3 0
|>
|>yup, you end up with a nobody owned copy of /dev/mem.
|
|This is not an NFS problem, since it is equally applicable to
|non-superusers on a local machine: it is simply a hint that
|mknod should be root-only. :-)

On all SunOS that I have access to (3.2, 3.5, 4.0) I got this when I try.

mknod: must be super-user

So it is a NFS problem.

Sven-Ove Westberg, CAD, University of Lulea, S-951 87 Lulea, Sweden.
Internet: sow@cad.luth.se