Missing fork() handling and pitfalls #10

Открыто
открыта 2021-08-09 20:17:19 +02:00 crtxcr · комментариев: 0
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 добавил(а) метки
bug
enhancement
2021-08-09 20:17:19 +02:00
Войдите, чтобы присоединиться к обсуждению.
1 участников
Уведомления
Срок выполнения
Срок выполнения не установлен.
Зависимости

Зависимостей нет.

Ссылка: crtxcr/exile.h#10
Описание отсутствует.