Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: dan robinson <dgrobinson@dgrobinson.com>
To: buildroot@busybox.net
Subject: [Buildroot] root permissions issue (reformatted)
Date: Wed, 14 Dec 2011 11:07:54 -0800 (PST)	[thread overview]
Message-ID: <32975352.post@talk.nabble.com> (raw)
In-Reply-To: <32975350.post@talk.nabble.com>


Okay, I think I have this figured out.  The NFS server is setting the file
owner's UID to 65534, which is the user 'nobody' on the server.  The NFS
client does not have root write permissions on the NFS server's filessytem.  

This came out of an investigation into why I couldn't log into a vanilla
buildroot built system.  Shadow passwords is on, but the root password in
the shadow file was blank.

--dan robinson

dan robinson wrote:
> 
> I have an NFS mounted root.  The directory, on the NFS server, does not
> have write permissions for 'other'.  I am not able to create a file when I
> run the command, 'touch one'.  On the NFS server side, I run 'chmod o+w'
> and that is shown in the second 'ls' command.  I can create a file.
> 
> If I 'su' to default, I can create files in that user's directory.
> 
> Note that the file, 'one', is owned by 65534.  I have included the
> /etc/passwd file.  This is -2 in 16 bits.  Noteworthy?
> 
> I ran the 'id' command.
> # id
> uid=0(root) gid=0(root) groups=0(root),10(wheel)
> 
> Ideas?
> 
> --dan robinson
> 
> 
> 
> # ls -al
> total 20
> drwxrwxr-x    2 root     root          4096 Dec 14  2011 .
> drwxr-xr-x   16 root     root          4096 Dec  7  2011 ..
> -rw-------    1 65534    65534          104 Dec 14  2011 .ash_history
> -rw-r--r--    1 root     root             0 Nov 30  2011 .bash_history
> -rw-r--r--    1 root     root           175 Nov 30  2011 .bash_logout
> -rw-r--r--    1 root     root           161 Nov 30  2011 .bash_profile
> # touch one
> touch: one: Permission denied
> 
> // chmod o+w has been run on NFS server
> # ls -al
> total 20
> drwxrwxrwx    2 root     root          4096 Dec 14  2011 .
> 
> drwxr-xr-x   16 root     root          4096 Dec  7  2011 ..
> -rw-------    1 65534    65534          121 Dec 14  2011 .ash_history
> -rw-r--r--    1 root     root             0 Nov 30  2011 .bash_history
> -rw-r--r--    1 root     root           175 Nov 30  2011 .bash_logout
> -rw-r--r--    1 root     root           161 Nov 30  2011 .bash_profile
> # touch one
> # ls -al
> total 20
> drwxrwxrwx    2 root     root          4096 Dec 14  2011 .
> drwxr-xr-x   16 root     root          4096 Dec  7  2011 ..
> -rw-------    1 65534    65534          138 Dec 14  2011 .ash_history
> -rw-r--r--    1 root     root             0 Nov 30  2011 .bash_history
> -rw-r--r--    1 root     root           175 Nov 30  2011 .bash_logout
> -rw-r--r--    1 root     root           161 Nov 30  2011 .bash_profile
> -rw-r--r--    1 65534    65534            0 Dec 14  2011 one
> 
> # cat /etc/passwd
> root::0:0:root:/root:/bin/sh
> daemon:x:1:1:daemon:/usr/sbin:/bin/sh
> bin:x:2:2:bin:/bin:/bin/sh
> sys:x:3:3:sys:/dev:/bin/sh
> sync:x:4:100:sync:/bin:/bin/sync
> mail:x:8:8:mail:/var/spool/mail:/bin/sh
> proxy:x:13:13:proxy:/bin:/bin/sh
> www-data:x:33:33:www-data:/var/www:/bin/sh
> backup:x:34:34:backup:/var/backups:/bin/sh
> operator:x:37:37:Operator:/var:/bin/sh
> haldaemon:x:68:68:hald:/:/bin/sh
> dbus:x:81:81:dbus:/var/run/dbus:/bin/sh
> ftp:x:83:83:ftp:/home/ftp:/bin/sh
> nobody:x:99:99:nobody:/home:/bin/sh
> sshd:x:103:99:Operator:/var:/bin/sh
> default:x:1000:1000:Default non-root user:/home/default:/bin/sh
> 
> 
> 

-- 
View this message in context: http://old.nabble.com/root-permissions-issue-%28reformatted%29-tp32975350p32975352.html
Sent from the Buildroot (busybox) mailing list archive at Nabble.com.

      parent reply	other threads:[~2011-12-14 19:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-14 18:58 [Buildroot] root permissions issue (reformatted) dan robinson
2011-12-14 19:01 ` Gustavo Zacarias
2011-12-14 19:07 ` dan robinson [this message]

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=32975352.post@talk.nabble.com \
    --to=dgrobinson@dgrobinson.com \
    --cc=buildroot@busybox.net \
    /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