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 加入了

bug

enhancement

標籤 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

登入才能加入這對話。