mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: erik.tews@gmx.net (Erik Tews)
To: linux-kernel@vger.kernel.org
Subject: Re: Two fixes for 2.4.19-pre5-ac3
Date: Mon, 8 Apr 2002 01:31:22 +0200	[thread overview]
Message-ID: <20020407233122.GA9883@no-maam.dyndns.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0204071240360.15439-100000@atx.fast.net> <E16uGg1-0006Ln-00@the-village.bc.nu>

On Sun, Apr 07, 2002 at 06:42:05PM +0100, Alan Cox wrote:
> > And, unless this is reversed the OpenAFS kernel module won't load (it 
> > needs sys_call_table.):
> 
> Correct. There was agreement a very long time ago that code should not patch
> the syscall table (for one its not safe). AFS probably needs fixing so the
> AFS syscall hook is exported portably and nicely in the syscall code.

I am really not an expert on kernel-programming but I remember that
there was a security-hole in the ptrace-code with which one a local user
could gain root access. And there was a little kernel-modul with a
wrapper-function for the ptrace-syscall that made traces only possible
if the user who was calling this syscall was root. So if I understand
right if we don't export the syscall-table it is impossible to write
such syscall-wrapper-functions and it requires to recompile the kernel
and reboot the machiene to fix such an security-hole.

So wouldn't it be better to export the syscall-table and just write into
the documentation that it is not a good idea to manipulate syscalls or
write a compiler-makro that gives out a warning when such a module is
beeing compiled.

  parent reply	other threads:[~2002-04-07 23:33 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-07 16:43 Steven N. Hirsch
2002-04-07 17:11 ` Christoph Hellwig
2002-04-07 17:14   ` arjan
2002-04-07 17:42 ` Alan Cox
2002-04-07 17:27   ` arjan
2002-04-07 17:48     ` Alexander Viro
2002-04-07 17:33   ` John Levon
2002-04-07 19:18     ` Alan Cox
2002-04-07 19:23       ` John Levon
2002-04-07 19:42         ` Alan Cox
2002-04-07 19:32           ` John Levon
2002-04-07 19:58             ` Alan Cox
2002-04-07 19:40       ` Jan Harkes
2002-04-07 20:01         ` Alan Cox
2002-04-07 20:13           ` Jan Harkes
2002-04-07 19:49     ` Alan Cox
2002-04-07 19:41       ` John Levon
2002-04-07 19:55         ` Muli Ben-Yehuda
2002-04-07 20:29           ` Alan Cox
2002-04-07 20:23             ` Muli Ben-Yehuda
2002-04-07 20:51               ` Alan Cox
2002-04-07 23:03               ` Anton Altaparmakov
2002-04-08  6:27                 ` Muli Ben-Yehuda
2002-04-07 20:02         ` Alan Cox
2002-04-07 20:10         ` Eric W. Biederman
2002-04-07 23:06           ` John Levon
2002-04-07 19:44       ` Steven N. Hirsch
2002-04-08 14:48     ` Bill Davidsen
2002-04-08 16:06       ` Philippe Elie
2002-04-08 17:53         ` Eric W. Biederman
2002-04-08 18:07           ` John Levon
2002-04-07 23:31   ` Erik Tews [this message]
     [not found] <20020407193245.GA21570@compsoc.man.ac.uk.suse.lists.linux.kernel>
     [not found] ` <E16uIoN-0006b3-00@the-village.bc.nu.suse.lists.linux.kernel>
2002-04-07 21:34   ` Andi Kleen

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=20020407233122.GA9883@no-maam.dyndns.org \
    --to=erik.tews@gmx.net \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®