Re: Ptrace patch for 2.4.x BREAKS kill() 2 interesting effects for .pid and dot locking? (was Re: Ptrace hole / Linux 2.2.25)

To: Matthew Grant <grantma@anathoth.gen.nz>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, Marcelo Tosatti <marcelo@conectiva.com.br>, debian-security@lists.debian.org, Herbert Xu <herbert@debian.org>
Subject: Re: Ptrace patch for 2.4.x BREAKS kill() 2 interesting effects for .pid and dot locking? (was Re: Ptrace hole / Linux 2.2.25)
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
Date: 20 Mar 2003 01:39:05 +0000
Message-id: <[🔎] 1048124344.708.15.camel@irongate.swansea.linux.org.uk>
In-reply-to: <[🔎] 1048113787.23160.21.camel@luther>
References: <1048104545.20129.24.camel@zion> <1048109690.23160.5.camel@luther> <[🔎] 1048113787.23160.21.camel@luther>

On Wed, 2003-03-19 at 22:43, Matthew Grant wrote:
> I have been just digging harder, and the vulnerability is only
> exploitable if you are using the kernel auto module loader, so compile

Not the case in some situations

> Could I please say this to the kernel developers, please fix it
> properly!

I take patches.

Alan

Reply to:

References:
- Ptrace patch for 2.4.x BREAKS kill() 2 interesting effects for .pid and dot locking? (was Re: Ptrace hole / Linux 2.2.25)
  - From: Matthew Grant <grantma@anathoth.gen.nz>

Prev by Date: Re: Ptrace patch for 2.4.x BREAKS kill() 2 interesting effects for .pid and dot locking? (was Re: Ptrace hole / Linux 2.2.25)
Next by Date: Re: OT: Is it so easy to break into an NIS?
Previous by thread: Re: Ptrace patch for 2.4.x BREAKS kill() 2 interesting effects for .pid and dot locking? (was Re: Ptrace hole / Linux 2.2.25)
Next by thread: Re: Ptrace patch for 2.4.x BREAKS kill() 2 interesting effects for .pid and dot locking? (was Re: Ptrace hole / Linux 2.2.25)
Index(es):
- Date
- Thread