Hi, It seems the "dpath" promise isn't documented in pledge(2) man page.
Technically, with "dpath" you have only access to mkfifo(2) and mknod(2) system calls. No more promises are need for create the files. If you request a mode with setuid/setgid/sticky bits, there are ignored. It is already documented in "Some system calls have restrictions applied to them" list. I dunno if "special files" is the right expression for saying "FIFO file" and "special file node" (if I take words from man pages of mkfifo(2) and mknod(2)). Comments ? OK ? -- Sebastien Marie Index: lib/libc/sys/pledge.2 =================================================================== RCS file: /cvs/src/lib/libc/sys/pledge.2,v retrieving revision 1.20 diff -u -p -r1.20 pledge.2 --- lib/libc/sys/pledge.2 16 Dec 2015 08:27:32 -0000 1.20 +++ lib/libc/sys/pledge.2 16 Dec 2015 08:59:13 -0000 @@ -254,6 +254,12 @@ create new files or directories in the f .Xr unlinkat 2 , .Xr mkdir 2 , .Xr mkdirat 2 . +.It Va "dpath" +A number of system calls are allowed and may cause +special file creation on the filesystem: +.Pp +.Xr mkfifo 2 , +.Xr mknod 2 . .It Va "tmppath" A number of system calls are allowed to do operations in the .Pa /tmp
