diff options
| author | Theo de Raadt <deraadt@cvs.openbsd.org> | 2016-05-27 19:45:05 +0000 |
|---|---|---|
| committer | Theo de Raadt <deraadt@cvs.openbsd.org> | 2016-05-27 19:45:05 +0000 |
| commit | 78b5afaf3f7a760112fbfce28204da6440738775 (patch) | |
| tree | 0a7f3cad12fe378e14e0b60deee9ab6a5bcd3e7d /sbin/mount_ffs | |
| parent | 7460ea7c8796fa4a440ed3fc75c19fe120c96c5d (diff) | |
W^X violations are no longer permitted by default. A kernel log message
is generated, and mprotect/mmap return ENOTSUP. If the sysctl(8) flag
kern.wxabort is set then a SIGABRT occurs instead, for gdb use or coredump
creation.
W^X violating programs can be permitted on a ffs/nfs filesystem-basis,
using the "wxallowed" mount option. One day far in the future
upstream software developers will understand that W^X violations are a
tremendously risky practice and that style of programming will be
banished outright. Until then, we recommend most users need to use the
wxallowed option on their /usr/local filesystem. At least your other
filesystems don't permit such programs.
ok jca kettenis mlarkin natano
Diffstat (limited to 'sbin/mount_ffs')
| -rw-r--r-- | sbin/mount_ffs/mount_ffs.c | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/sbin/mount_ffs/mount_ffs.c b/sbin/mount_ffs/mount_ffs.c index f2c5ee2568a..98b8ad795cc 100644 --- a/sbin/mount_ffs/mount_ffs.c +++ b/sbin/mount_ffs/mount_ffs.c @@ -1,4 +1,4 @@ -/* $OpenBSD: mount_ffs.c,v 1.22 2015/12/08 15:56:42 tedu Exp $ */ +/* $OpenBSD: mount_ffs.c,v 1.23 2016/05/27 19:45:04 deraadt Exp $ */ /* $NetBSD: mount_ffs.c,v 1.3 1996/04/13 01:31:19 jtc Exp $ */ /*- @@ -47,6 +47,7 @@ void ffs_usage(void); static const struct mntopt mopts[] = { MOPT_STDOPTS, + MOPT_WXALLOWED, MOPT_ASYNC, MOPT_SYNC, MOPT_UPDATE, |