summaryrefslogtreecommitdiffstats
path: root/.github
diff options
context:
space:
mode:
authorderaadt@openbsd.org <deraadt@openbsd.org>2021-10-24 23:24:17 +0200
committerDamien Miller <djm@mindrot.org>2021-10-28 04:56:59 +0200
commitd4bed5445646e605c383a4374fa962e23bf9e3a3 (patch)
treeadfeeee668d57fc44127dc503c956f376e03cec6 /.github
parentkitchensink test target now needs krb5. (diff)
downloadopenssh-d4bed5445646e605c383a4374fa962e23bf9e3a3.tar.xz
openssh-d4bed5445646e605c383a4374fa962e23bf9e3a3.zip
upstream: 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 OpenBSD-Commit-ID: 503d11633497115688c0c6952686524f01f53121
Diffstat (limited to '.github')
0 files changed, 0 insertions, 0 deletions