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]
Date:	Wed, 16 Apr 2008 19:13:44 +0200
From:	maximilian attems <max@...o.at>
To:	Eric Paris <eparis@...hat.com>
Cc:	James Morris <jmorris@...ei.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org,
	Russell King <rmk+kernel@....linux.org.uk>,
	maximilian attems <max@...o.at>,
	Martin Michlmayr <tbm@...ius.com>,
	Gordon Farquharson <gordonfarquharson@...il.com>
Subject: [PATCH] Kconfig: enhance DEFAULT_MMAP_MIN_ADDR description

Got burned by setting the proposed default of 65536
across all Debian archs.

Thus proposing to be more specific on which archs you may
set this. Also propose a value for arm and friends that
doesn't break sshd.

Signed-off-by: maximilian attems <max@...o.at>
Cc: Martin Michlmayr <tbm@...ius.com>
Cc: Gordon Farquharson <gordonfarquharson@...il.com>
---
 security/Kconfig |    5 +++--
 1 files changed, 3 insertions(+), 2 deletions(-)

diff --git a/security/Kconfig b/security/Kconfig
index 5dfc206..cc1e4bd 100644
--- a/security/Kconfig
+++ b/security/Kconfig
@@ -113,8 +113,9 @@ config SECURITY_DEFAULT_MMAP_MIN_ADDR
 	  from userspace allocation.  Keeping a user from writing to low pages
 	  can help reduce the impact of kernel NULL pointer bugs.
 
-	  For most users with lots of address space a value of 65536 is
-	  reasonable and should cause no problems.  Programs which use vm86
+	  For most x86 users with lots of address space a value of 65536 is
+	  reasonable and should cause no problems. On arm and other archs
+	  it should not be higher than 32768. Programs which use vm86
 	  functionality would either need additional permissions from either
 	  the LSM or the capabilities module or have this protection disabled.
 
-- 
1.5.5

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