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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sat, 7 Oct 2006 11:23:01 +0000
From:	Pavel Machek <pavel@....cz>
To:	Michael Buesch <mb@...sch.de>
Cc:	Alan Cox <alan@...rguk.ukuu.org.uk>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: Really good idea to allow mmap(0, FIXED)?

Hi!
> 
> > > Besides that, I currently don't see a valid reason to mmap address 0.
> > > 
> > > Comments?
> > 
> > User zero is not neccessarily mapped at kernel zero so your argument
> > isn't portable either.
> 
> Eh, so what about the following.
> We _have_ arches which map user zero to kernel zero. What about
> specialcasing that on a per-arch case. So remapping user zero to
> something else in kernel.

Just add some magic constant on architectures you care about... make
user 0 start at 4mb in kernel... and you get your security hardened
kernel w/o breaking dosemu. All you need is to create a patch :-)


-- 
Thanks for all the (sleeping) penguins.
-
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ