linux-kernel - Re: [PATCH] Undo some of the pseudo-security madness

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: <87mz4996wg.wl@betelheise.deep.net>
Date:	Tue, 23 Jan 2007 17:03:59 +0300
From:	Samium Gromoff <_deepfire@...lingofgreen.ru>
To:	Pavel Machek <pavel@....cz>
Cc:	Samium Gromoff <_deepfire@...lingofgreen.ru>,
	Valdis.Kletnieks@...edu, David Wagner <daw@...berkeley.edu>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Undo some of the pseudo-security madness

At Tue, 23 Jan 2007 08:48:07 +0000,
Pavel Machek wrote:
> > Are you saying that the usefulness of AS randomisation is
> > overall exceeding that of MAP_FIXED, and the latter should be
> > abolished?
> 
> MAP_FIXED still works. You just have to be more careful where you map.

No amount of carefulness will prevent vendors stick arbitrarily
damaging values of stack and mmap base randomisation, severely reducing
the usefullness of MAP_FIXED.

And they actively take this freedom -- Arjan must know this first-hand.

> > > > the only way to achieve this i see, is to directly setuid root
> > > > the lisp system executable itself -- because the lisp code
> > > > is read, compiled and executed in the process of the lisp
> > > > system executable.
> > > 
> > > If that's the only way you can see to do it, maybe you should think a
> > > bit harder before making kernel hacks to do something.
> > 
> > I want equal grounds for platforms, that`s all.
> 
> Well, noone ever said all languages are equal. You have crappy lisp
> interpreters, and you want to break kernel because you are too lazy to
> fix them, and insist they must do suid in any way you choose. We won't
> break kernel because lisp is misdesigned.

SBCL is the most actively developed open source Common Lisp implementation,
which has an optimising native compiler built in, so it is not an interpreter,
and is, most certainly, not crappy.

Speaking on the matter, how would you regard a patch which enhances
the ELF loader with interpretation of an x86-specific e_flags bit
which would mean a mandatory AS randomisation disable?

this has the following properties:

1. cannot serve as a vehicle for exploitation for binaries unmarked
with this flag
2. serve the application deployment cause -- abolish the need for
application-specific system tweaks
3. remove the need for the ugly self-reexecution tweak people
needing an absolutely unadulterated memory map have to resort to /now/,
even in a non-setuid case 

> 							Pavel

P.S.:
Please, shrug off that C-esque center-of-the-world attitude,
the fact there are thousand times as many C programmers does not
automatically mean there is a free-for-all no-questions-asked
licence to raise the implementation complexity bar for other languages.

regards, Samium Gromoff
-
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/