Missing fork() handling and pitfalls #10

Buka
di buka 2021-08-09 20:17:19 +02:00 oleh crtxcr · 0 komentar
Pemilik

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
Masuk untuk bergabung dengan percakapan ini.
Tidak Ada Milestone
No Assignees
1 peserta
Notifikasi
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: crtxcr/exile.h#10
No description provided.