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 于 2021-08-09 20:17:19 +02:00 添加了标签

bug

enhancement

crtxcr 于

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

在代码提交中引用了该工单

Close file fds by default, introduce policy->keep_fds_open

登录并参与到对话中。