linux-kernel - [PATCH 0/2] x86: allow to enable/disable modify

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

Message-Id: <1438626217-23970-1-git-send-email-w@1wt.eu>
Date:	Mon,  3 Aug 2015 20:23:35 +0200
From:	Willy Tarreau <w@....eu>
To:	Andy Lutomirski <luto@...nel.org>,
	Kees Cook <keescook@...omium.org>
Cc:	Willy Tarreau <w@....eu>, Steven Rostedt <rostedt@...dmis.org>,
	"security@...nel.org" <security@...nel.org>,
	X86 ML <x86@...nel.org>, Borislav Petkov <bp@...en8.de>,
	Sasha Levin <sasha.levin@...cle.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
	Boris Ostrovsky <boris.ostrovsky@...cle.com>,
	Andrew Cooper <andrew.cooper3@...rix.com>,
	Jan Beulich <jbeulich@...e.com>,
	xen-devel <xen-devel@...ts.xen.org>
Subject: [PATCH 0/2] x86: allow to enable/disable modify_ldt at run time

This is the second version. It adds a strategy for the sysctls so that we
can reject any change to a value that was already negative. This way it's
possible to disable modify_ldt temporarily or permanently (eg: lock down a
server) as suggested by Kees.

Willy Tarreau (2):
  sysctl: add a new generic strategy to make permanent changes on
    negative values
  x86/ldt: allow to disable modify_ldt at runtime

 Documentation/sysctl/kernel.txt | 16 +++++++++++++
 arch/x86/Kconfig                | 17 ++++++++++++++
 arch/x86/kernel/ldt.c           | 15 +++++++++++++
 kernel/sysctl.c                 | 50 +++++++++++++++++++++++++++++++++++++++++
 4 files changed, 98 insertions(+)

-- 
1.7.12.1

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