linux-kernel - Re: why is intercepting system calls considerred bad?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <bda6d13a0607202234xc7d58a1t2a440c8458596582@mail.gmail.com>
Date:	Thu, 20 Jul 2006 22:34:08 -0700
From:	"Joshua Hudson" <joshudson@...il.com>
To:	"Irfan Habib" <irfan.habib@...il.com>, linux-kernel@...r.kernel.org
Subject: Re: why is intercepting system calls considerred bad?

On 7/20/06, Irfan Habib <irfan.habib@...il.com> wrote:
> HI,
>
> I recently met a kernel janitor, who told me that intercepting system
> calls is undesirable, why?

I'll bite.

You intercept. Somebody else intercepts. You want to stop intercepting.

For this reason, anybody who intercepts a system call must be compiled
in, and if two intercept the same system call, than the link order
dictates behavior.

Obviously not desirable.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/