From: Daniel Jacobowitz <dan@debian.org>
To: Adam Majer <adamm@galacticasoftware.com>
Cc: Bernhard Kaindl <bk@suse.de>,
linux-kernel@vger.kernel.org,
Marcelo Tosatti <marcelo@conectiva.com.br>
Subject: Re: ptrace secfix does NOT work... :(
Date: Sat, 10 May 2003 17:11:54 -0400 [thread overview]
Message-ID: <20030510211154.GA4559@nevyn.them.org> (raw)
In-Reply-To: <20030510205249.GA1179@galacticasoftware.com>
On Sat, May 10, 2003 at 03:52:49PM -0500, Adam Majer wrote:
> On Fri, May 09, 2003 at 12:05:52AM +0200, Bernhard Kaindl wrote:
> > Hello,
> >
> > The attached patch cleans up the too restrictive checks which were
> > included in the original ptrace/kmod secfix posted by Alan Cox
> > and applies on top of a clean 2.4.20-rc1 source tree.
>
> But the ptrace hole is _NOT_ fixed... :(
This is the exploit which makes itself suid. Did you leave it suid
before retesting it?
> adamm@polaris:~/test$ uname -r
> 2.4.21-rc2
> \u@\h:\w\$ ls -ltr hehe
> -rw------- 1 root root 17 May 10 15:44 hehe
> \u@\h:\w\$ whoami
> root
> \u@\h:\w\$ cat hehe
> I can see you!!
>
> \u@\h:\w\$ rm hehh
> \u@\h:\w\$ ls -ltr hehe
> ls: hehe: No such file or directory
Huh?
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-05-10 20:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-08 22:05 [PATCH][2.4] cleanup ptrace secfix and fix most side effects Bernhard Kaindl
2003-05-08 21:31 ` Alan Cox
2003-05-08 22:48 ` Alan Cox
2003-05-08 23:59 ` Bernhard Kaindl
2003-05-09 0:17 ` Bernhard Kaindl
2003-05-10 20:52 ` ptrace secfix does NOT work... :( Adam Majer
2003-05-10 21:11 ` Daniel Jacobowitz [this message]
2003-05-10 21:25 ` Adam Majer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030510211154.GA4559@nevyn.them.org \
--to=dan@debian.org \
--cc=adamm@galacticasoftware.com \
--cc=bk@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.