From aeda2bc1482c038af48f66f417a485587f2cafc1 Mon Sep 17 00:00:00 2001 From: deraadt Date: Sat, 17 Oct 2015 23:50:04 +0000 Subject: [PATCH] naddy asks me if __tfork should be allowed by "proc". yes! We may need a better semantic later ("thread"?), but this allows progress, and people can report their experiences. --- sys/kern/kern_pledge.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/sys/kern/kern_pledge.c b/sys/kern/kern_pledge.c index c4f47f88fb9..a3f8a09b14e 100644 --- a/sys/kern/kern_pledge.c +++ b/sys/kern/kern_pledge.c @@ -1,4 +1,4 @@ -/* $OpenBSD: kern_pledge.c,v 1.47 2015/10/17 23:12:46 deraadt Exp $ */ +/* $OpenBSD: kern_pledge.c,v 1.48 2015/10/17 23:50:04 deraadt Exp $ */ /* * Copyright (c) 2015 Nicholas Marriott @@ -89,6 +89,7 @@ const u_int pledge_syscalls[SYS_MAXSYSCALL] = { [SYS_fchdir] = PLEDGE_SELF, /* careful of directory fd inside jails */ /* needed by threaded programs */ + [SYS___tfork] = PLEDGE_PROC, [SYS_sched_yield] = PLEDGE_SELF, [SYS___thrsleep] = PLEDGE_SELF, [SYS___thrwakeup] = PLEDGE_SELF, -- 2.20.1