summaryrefslogtreecommitdiffstats
path: root/usr.bin/tmux/cmd-load-buffer.c
diff options
context:
space:
mode:
authorderaadt <deraadt@openbsd.org>2015-11-14 07:02:23 +0000
committerderaadt <deraadt@openbsd.org>2015-11-14 07:02:23 +0000
commit0ecb303c31c9af196f044e5249c8c1c954f62ed1 (patch)
treea001e566856541ab92338bb8bcf7411a93ab7059 /usr.bin/tmux/cmd-load-buffer.c
parentFix a missing unlock. (diff)
downloadwireguard-openbsd-0ecb303c31c9af196f044e5249c8c1c954f62ed1.tar.xz
wireguard-openbsd-0ecb303c31c9af196f044e5249c8c1c954f62ed1.zip
For pledge "stdio", allow the break(2) system call which backends the brk/sbrk
library routines. The manpage declares, in bold: The brk() and sbrk() functions are historical curiosities left over from earlier days before the advent of virtual memory management. In our base tree, only one program uses these functions -- cc1 in the gcc toolset. A historical curiosity using a historical curiosity, how quaint. brk is used because precompiled c headers are not position independent. Another program which relies upon brk is emacs. Other uses of brk are EXCEEDINGLY RARE, because most software grew up and use modern practices such as malloc and mmap, thereby gaining ASLR benefits. Position independence has become an important part of mitigations. These two programs fight such improvements. Permitting brk/sbrk allows the large attack surface of cc1 to be pledged. "I would rather have cc1 pledged than purity in pledge" guenther
Diffstat (limited to 'usr.bin/tmux/cmd-load-buffer.c')
0 files changed, 0 insertions, 0 deletions