Missing fork() handling and pitfalls #10

建立問題

crtxcr · 2021-08-09T20:17:19+02:00

crtxcr " 評論

2021-08-09 20:17:19 +02:00

"

管理員

We don't do fork()/clone() ourselves, opening the door for many pitfalls, e. g. we inherit open file descriptories which may enable bypassing of the policies we set. Otoh, some open fd's may actually be desired.

We must either offer a safe fork()/clone() or check that the current process is in a reasonable state and/or transform to that state.

We don't do fork()/clone() ourselves, opening the door for many pitfalls, e. g. we inherit open file descriptories which may enable bypassing of the policies we set. Otoh, some open fd's may actually be desired. We must either offer a safe fork()/clone() or check that the current process is in a reasonable state and/or transform to that state.

crtxcr added the

bug

enhancement

label 2021-08-09 20:17:19 +02:00

crtxcr 在代碼提交

2022-07-17 13:01:24 +02:00

中引用了該問題

Close file fds by default, introduce policy->keep_fds_open

登入才能加入這對話。