Missing fork() handling and pitfalls #10

Jauna problēma

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

crtxcr komentēja

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

Īpašnieks

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 pievienoja

bug

enhancement

etiķetes 2021-08-09 20:17:19 +02:00

crtxcr pieminēja šo problēmu revīzijā

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

Close file fds by default, introduce policy->keep_fds_open

Nepieciešams pieteikties, lai pievienotos šai sarunai.