linux-kernel - Re: System call interposition/unprotecting the table

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: <Pine.LNX.4.64.0708142308530.10912@fbirervta.pbzchgretzou.qr>
Date:	Tue, 14 Aug 2007 23:09:56 +0200 (CEST)
From:	Jan Engelhardt <jengelh@...putergmbh.de>
To:	Andi Kleen <andi@...stfloor.org>
cc:	Hajime Inoue <hinoue@...l.carleton.ca>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	linux-kernel@...r.kernel.org
Subject: Re: System call interposition/unprotecting the table


On Aug 14 2007 21:50, Andi Kleen wrote:
>Hajime Inoue <hinoue@...l.carleton.ca> writes:
>
>> Just protecting the table does not stop rootkits.  A highly referenced
>> phrack article explains how to bypass the table. 
>
>During .23-pre for some time the kernel text was protected too (that
>would have likely stopped that particular attack), but it was
>removed because it caused too many problems.
>
>Ultimatively it is useless for security anyways because the page
>tables cannot be protected (because there are valid reasons to change
>them).

But with DEBUG_RODATA (does that also apply to .text?) enabled,
accidental writes to it should cause a fault rather than doing silent
changes, would not it?


	Jan
-- 
-
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/