linux-kernel - mmap_min_addr/SECURITY_DEFAULT_MMAP_MIN

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-next>] [day] [month] [year] [list]

Message-ID: <20080623135337.GE846@gallifrey>
Date:	Mon, 23 Jun 2008 14:53:37 +0100
From:	"Dr. David Alan Gilbert" <linux@...blig.org>
To:	linux-kernel@...r.kernel.org
Subject: mmap_min_addr/SECURITY_DEFAULT_MMAP_MIN_ADDR suggested values

Hi,
  The config help for SECURITY_DEFAULT_MMAP_MIN_ADDR suggests 65536
as a 'reasonable' value for x86 and the original mmap_min_addr
patches suggested that 'something like 64k' was a safe value that
wouldn't affect most programs.

  Where does this 64k value come from?  A number of distros seem
to have followed this advice and have it set to 64k; but is there
really any likely benefit of having it larger than PAGE_SIZE say?

I ask because I have an ancient program that maps stuff at 8k; the
general advice of stuff on the net seems to be to set this limit
to 0 if people have problems (I'm just lowering it to 4k),
but I was thinking perhaps using a lower default value would be more
secure since less people would take the easy answer and just turn the
feature off altogether.

Dave

-- 
 -----Open up your eyes, open up your mind, open up your code -------   
/ Dr. David Alan Gilbert    | Running GNU/Linux on Alpha,68K| Happy  \ 
\ gro.gilbert @ treblig.org | MIPS,x86,ARM,SPARC,PPC & HPPA | In Hex /
 \ _________________________|_____ http://www.treblig.org   |_______/
--
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/