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

labels 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

"로그인하여 이 대화에 참여"