Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sven Neumann <neumann@teufel.de>
To: buildroot@busybox.net
Subject: [Buildroot] Default target file system permissions
Date: Thu, 31 Oct 2013 23:42:14 +0100	[thread overview]
Message-ID: <1383259334.10813.7.camel@bender> (raw)

Hi,

I've been debugging some problems with our buildroot builds lately and
found them to be caused by too restrictive permissions on the target
file system. Pretty much all files and directories, unless specified
explicitly in system/device_table.txt are only readable by the owner
(root). This causes problems with samba (/var/nmbd not accessible by
nmbd), dbus services (dbus daemon can not access the service files) and
so on. Basically only services that are running as root can work
correctly, because for other users the system is pretty much
inaccessible. I've come across this mail on the mailing-list which seems
related, but couldn't find an answer:
http://buildroot-busybox.2317881.n4.nabble.com/Default-target-file-system-permissions-td39088.html


Here's how the root folder on our target file-system looks like: 

drwxr-xr-x   20 root     root          4096 Dec  7  1999 .
drwxr-xr-x   20 root     root          4096 Dec  7  1999 ..
drwx------    2 root     root          4096 Dec  7  1999 bin
drwxr-xr-x    2 root     root          4096 Nov 30  1999 boot
drwxr-xr-x    5 root     root          4096 Dec 30  1999 data
drwxr-xr-x   10 root     root         12600 Dec  7  1999 dev
drwxr-xr-x   15 root     root          4096 Dec  7  1999 etc
drwx------    3 root     root          4096 Dec  7  1999 home
drwx------    4 root     root          4096 Dec  7  1999 lib
lrwxrwxrwx    1 root     root            11 Oct 31 20:26 linuxrc ->
bin/busybox
drwx------    2 root     root          4096 Dec  7  1999 media
drwx------    2 root     root          4096 Dec  7  1999 mnt
drwx------    2 root     root          4096 Dec  7  1999 opt
dr-xr-xr-x   62 root     root             0 Dec  7  1999 proc
drwx------    2 root     root          4096 Oct 31 22:09 root
lrwxrwxrwx    1 root     root             3 Oct 31 18:39 run -> tmp
drwx------    2 root     root          4096 Dec  7  1999 sbin
dr-xr-xr-x   11 root     root             0 Dec  7  1999 sys
drwxrwxrwt   12 root     root           800 Oct 31 21:51 tmp
drwx------    7 root     root          4096 Dec  7  1999 usr
drwxr-xr-x    7 root     root          4096 Dec  7  1999 var


So are the restrictive permissions on the target file-system intentional
and how I can change this situation?


Regards,
Sven

             reply	other threads:[~2013-10-31 22:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-31 22:42 Sven Neumann [this message]
2013-11-02 22:23 ` [Buildroot] Default target file system permissions Arnout Vandecappelle
  -- strict thread matches above, loose matches on Subject: below --
2013-11-02  8:13 Sven Neumann
2013-11-02 10:06 ` Thomas Petazzoni
2013-11-02 18:30   ` Sven Neumann
2013-01-21  4:38 Przemyslaw Wrzos

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=1383259334.10813.7.camel@bender \
    --to=neumann@teufel.de \
    --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