<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On 2 December 2015 at 23:16, Alejandro del Castillo <span dir="ltr"><<a href="mailto:alejandro.delcastillo@ni.com" target="_blank">alejandro.delcastillo@ni.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">> Whilst the patch is fine, this is worrying as noexec /tmp shouldn't break opkg.<br>
> Maybe opkg should be changed to use something in /var for the scripts?<br>
<br>
</span>Could you expand on why it's better to use /var instead of /tmp as the default<br>
sandbox location for opkg? I believe dpkg uses /var/lib/ and would like to<br>
understand why that's better (to change opkg, if it makes sense)</blockquote></div><br>Well in this case it's fairly common to mount /tmp as noexec on security grounds, and to be limited in size (say a small tmpfs), whereas /var generally has less restrictions.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Ross</div></div>