Re: Security implications of allowing init to re-exec from another path

To: Henrique de Moraes Holschuh <hmh@debian.org>
Cc: debian-security@lists.debian.org
Subject: Re: Security implications of allowing init to re-exec from another path
From: Michael Stone <mstone@debian.org>
Date: Thu, 05 Jan 2006 07:21:06 -0500
Message-id: <[🔎] 20060105122106.GD32630@mathom.us>
Mail-followup-to: Henrique de Moraes Holschuh <hmh@debian.org>, debian-security@lists.debian.org
In-reply-to: <[🔎] 20060105115459.GB10447@khazad-dum.debian.net>
References: <[🔎] 43BBE787.1020003@yahoo.co.uk> <[🔎] 20060105115459.GB10447@khazad-dum.debian.net>

On Thu, Jan 05, 2006 at 09:54:59AM -0200, Henrique de Moraes Holschuh wrote:

Just to make the question a bit more clear for those not reading the bug
report, the real question is, are we causing problems for people who run /
read-only (imagine read-only media) and their security expectations?


So make it configurable.

Reply to:

References:
- Security implications of allowing init to re-exec from another path
  - From: Thomas Hood <jdthood@yahoo.co.uk>
- Re: Security implications of allowing init to re-exec from another path
  - From: Henrique de Moraes Holschuh <hmh@debian.org>

Prev by Date: unsubscribe
Next by Date: Re: iptable: --seconds
Previous by thread: Re: Security implications of allowing init to re-exec from another path
Next by thread: Re: Security implications of allowing init to re-exec from another path
Index(es):
- Date
- Thread