diff options
author | deraadt@openbsd.org <deraadt@openbsd.org> | 2021-10-24 23:24:17 +0200 |
---|---|---|
committer | Damien Miller <djm@mindrot.org> | 2021-10-28 04:56:59 +0200 |
commit | d4bed5445646e605c383a4374fa962e23bf9e3a3 (patch) | |
tree | adfeeee668d57fc44127dc503c956f376e03cec6 /sshconnect.c | |
parent | kitchensink test target now needs krb5. (diff) | |
download | openssh-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 'sshconnect.c')
0 files changed, 0 insertions, 0 deletions