deraadt b7041c0781 For open/openat, if the flags parameter does not contain O_CREAT, the ... 3rd (variadic) mode_t parameter is irrelevant. Many developers in the past have passed mode_t (0, 044, 0644, or such), which might lead future people to copy this broken idiom, and perhaps even believe this parameter has some meaning or implication or application. Delete them all. This comes out of a conversation where tb@ noticed that a strange (but intentional) pledge behaviour is to always knock-out high-bits from mode_t on a number of system calls as a safety factor, and his bewilderment that this appeared to be happening against valid modes (at least visually), but no sorry, they are all irrelevant junk. They could all be 0xdeafbeef. ok millert		2021-10-24 21:24:15 +00:00
..
bpf.c	When system calls indicate an error they return -1, not some arbitrary	2019-06-28 13:32:41 +00:00
conf.c
defs.h
Makefile
parseconf.c	When system calls indicate an error they return -1, not some arbitrary	2019-06-28 13:32:41 +00:00
pathnames.h
rbootd.8	list example files in FILES with a short description: generally, "Example	2020-05-16 16:58:11 +00:00
rbootd.c	When system calls indicate an error they return -1, not some arbitrary	2019-06-28 13:32:41 +00:00
rmp_var.h
rmp.h
rmpproto.c	For open/openat, if the flags parameter does not contain O_CREAT, the	2021-10-24 21:24:15 +00:00
utils.c