Hi,
I've noticed that the file ownership of every file and directory in my /opt directory on my RT-N66U has its permissions reset to rwxrwxrwx and ownership reset to admin:root every time the system is rebooted. chown and chmod are effective but only until the system is rebooted. This problem has persisted across every firmware version that I remember. I'm currently running 3.0.0.4.374.34_2
My /opt is an alias of /mnt/sda2/asusware, the device is a traditional USB HDD and here is the output of the mount command:
rootfs on / type rootfs (rw)
/dev/root on / type squashfs (ro)
proc on /proc type proc (rw)
tmpfs on /tmp type tmpfs (rw)
devfs on /dev type tmpfs (rw,noatime)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw)
/dev/mtdblock4 on /jffs type jffs2 (rw,noatime)
usbfs on /proc/bus/usb type usbfs (rw)
/dev/sda1 on /tmp/mnt/Networked_Storage type ufsd (rw,nodev,noatime,nls=utf8,fma
sk=0,dmask=0,sparse,force)
/dev/sda2 on /tmp/mnt/sda2 type ext3 (rw,nodev,noatime,data=ordered)
The NTFS partition also has issues with not respecting permissions but that seems to be by design, as implied by the mount options.
Has anyone else encountered this problem before? I have Asterisk running under it's own Unix account and so need to have the permissions set appropriately (i.e. not world writeable) in order to gain any security advantage. I can workaround the problem by inserting various chown and chmod instructions into /jffs/scripts/post-mount but a nicer solution would be handy.
I've noticed that the file ownership of every file and directory in my /opt directory on my RT-N66U has its permissions reset to rwxrwxrwx and ownership reset to admin:root every time the system is rebooted. chown and chmod are effective but only until the system is rebooted. This problem has persisted across every firmware version that I remember. I'm currently running 3.0.0.4.374.34_2
My /opt is an alias of /mnt/sda2/asusware, the device is a traditional USB HDD and here is the output of the mount command:
rootfs on / type rootfs (rw)
/dev/root on / type squashfs (ro)
proc on /proc type proc (rw)
tmpfs on /tmp type tmpfs (rw)
devfs on /dev type tmpfs (rw,noatime)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw)
/dev/mtdblock4 on /jffs type jffs2 (rw,noatime)
usbfs on /proc/bus/usb type usbfs (rw)
/dev/sda1 on /tmp/mnt/Networked_Storage type ufsd (rw,nodev,noatime,nls=utf8,fma
sk=0,dmask=0,sparse,force)
/dev/sda2 on /tmp/mnt/sda2 type ext3 (rw,nodev,noatime,data=ordered)
The NTFS partition also has issues with not respecting permissions but that seems to be by design, as implied by the mount options.
Has anyone else encountered this problem before? I have Asterisk running under it's own Unix account and so need to have the permissions set appropriately (i.e. not world writeable) in order to gain any security advantage. I can workaround the problem by inserting various chown and chmod instructions into /jffs/scripts/post-mount but a nicer solution would be handy.
