I'm not sure what issue exactly you're having, but there is a step of tweaking the permissions just prior to building the filesystem image: https://dev.openwrt.org/browser/trunk/include/image.mk#L171
In my case the permissions on the dropbear host keys weren't being set properly, so I submitted this patch to fix it but it hasn't been committed yet: https://lists.openwrt.org/pipermail/openwrt-devel/2013-September/021553.html Actually, in my case there were further issues because I run with 'umask 0002' which sets too permissive modes on /etc/dropbear and trips some runtime safety checks at connection time. I had to further change the permissions tweaking like this: https://github.com/cpatulea/openwrt/commit/5cb9586437a947007748e89e60a760eaab7e87db but this patch I haven't submitted to openwrt-devel. On Fri, Oct 4, 2013 at 3:36 PM, Zoltan Gyarmati <[email protected]> wrote: > Hi, > > during my OpenWrt build i need to install some config files, for example > for dropbear. For this i add the files under the files, as per > http://wiki.openwrt.org/doc/howto/build#custom.files , > but it seems during the copy into the root fs, the file permissions are > not preserved. Is there anything to set these customs files permissions? > Something like the device_table.txt in the in Buildroot? If it's > possible i would like to solve this during image creation time, without > any openwrt patching or script running on the target. Thanks for any > hint in advance, > > > -- > br, > Zoltan Gyarmati > mail: [email protected] > freenode nick: zgyarmati > _______________________________________________ > openwrt-users mailing list > [email protected] > https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-users _______________________________________________ openwrt-users mailing list [email protected] https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-users
