Missing fork() handling and pitfalls #10

Questão nova

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

crtxcr comentou

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

Proprietário(a)

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 adicionou os rótulos

bug

enhancement

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

crtxcr referenciou esta questão num cometimento

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

Close file fds by default, introduce policy->keep_fds_open

Inicie a sessão para participar neste diálogo.