diff options
| author |   deraadt <deraadt@openbsd.org> | 2016-05-27 19:45:04 +0000 |
|---|---|---|
| committer | deraadt <deraadt@openbsd.org> | 2016-05-27 19:45:04 +0000 |
| commit | 9f25ea0444789356f96f36dfcfb511298f4ea099 (patch) | |
| tree | aafbce4074a5cde5dbdc3c3a5324bee65ac5545d /lib/libc/stdlib/nrand48.c | |
| parent | Use getprogname() instead of __progname to make portability easier. (diff) | |
| download | wireguard-openbsd-9f25ea0444789356f96f36dfcfb511298f4ea099.tar.xz wireguard-openbsd-9f25ea0444789356f96f36dfcfb511298f4ea099.zip | |
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 'lib/libc/stdlib/nrand48.c')
0 files changed, 0 insertions, 0 deletions