[radvd-devel-l] Insecure file permissions, but continuing anyway
Jim Paris
jim at jtan.com
Wed Aug 24 13:42:09 EDT 2011
Ron Hermsen wrote:
> Dear All,
>
> I was looking if I could "solve" the "Insecure file permissions, but
> continuing anyway" message I see in the syslog.
>
> I used "chmod 600 /mnt/radvd.conf" to make it only read/writeable by root
> (admin in my case), but that didn't solve it.
>
> Even with "chmod 000 /mnt/radvd.conf" it still gives the same message:
> ---------- 1 admin root 2927 Aug 20 2011 radvd.conf
>
> Jan 1 00:01:59 (none) daemon.info radvd[642]: version 1.8.1 started 74
> Jan 1 00:02:00 (none) daemon.warn radvd[642]: Insecure file permissions,
> but continuing anyway 101
>
> Any tips to solve this?
>
> This is a (uclibc based) ADSL router with the following user configured (no
> user root, but uses admin instead).
> # cat /etc/passwd
> admin:xxxx:0:0:Administrator:/:/bin/sh
> support:.xxxx.:0:0:Technical Support:/:/bin/sh
> user:xxxx:0:0:Normal User:/:/bin/sh
> #
>
> # env
> USER=root
> SHELL=/bin/sh
> PATH=/bin:/sbin:/usr/bin
> TERM=vt102
> HOME=/
> #
It's probably because getpwnam("root") is returning NULL.
You should add an entry for root to /etc/passwd. See
check_conffile_perm in radvd.c for the exact logic it's using.
-jim
More information about the radvd-devel-l
mailing list