Missing fork() handling and pitfalls #10

Neues Issue

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

crtxcr hat

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

kommentiert

Besitzer

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 hat die Labels

bug

enhancement

2021-08-09 20:17:19 +02:00 hinzugefügt

crtxcr hat dieses Issue

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

aus einem Commit referenziert

Close file fds by default, introduce policy->keep_fds_open

Anmelden, um an der Diskussion teilzunehmen.