From mboxrd@z Thu Jan 1 00:00:00 1970 X-Received: by 10.236.15.69 with SMTP id e45mr6050554yhe.5.1422022122442; Fri, 23 Jan 2015 06:08:42 -0800 (PST) X-BeenThere: voidlinux@googlegroups.com Received: by 10.107.40.71 with SMTP id o68ls5872ioo.61.gmail; Fri, 23 Jan 2015 06:08:42 -0800 (PST) X-Received: by 10.50.66.141 with SMTP id f13mr24493igt.17.1422022122234; Fri, 23 Jan 2015 06:08:42 -0800 (PST) Date: Fri, 23 Jan 2015 06:08:41 -0800 (PST) From: Antonio Malcolm To: voidlinux@googlegroups.com Message-Id: Subject: Can't mount /tmp with noexec?? MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_1562_1684195204.1422022121068" ------=_Part_1562_1684195204.1422022121068 Content-Type: multipart/alternative; boundary="----=_Part_1563_286842521.1422022121069" ------=_Part_1563_286842521.1422022121069 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Noticed this, fast. Mounting /tmp with noexec means I can't install packages, as attempting to do so results in a permissions error. Remounting without noexec resolves this issue, but I'd rather lock down /tmp, if possible. ------=_Part_1563_286842521.1422022121069 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit
Noticed this, fast. Mounting /tmp with noexec means I can't install packages, as attempting to do so results in a permissions error.
Remounting without noexec resolves this issue, but I'd rather lock down /tmp, if possible.
------=_Part_1563_286842521.1422022121069-- ------=_Part_1562_1684195204.1422022121068--