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>] [day] [month] [year] [list]
Message-ID: <CAD-N9QUf1GXdfFA0o0f6z1rvtBz0BUN745_pvt0CYa8ke74Y3A@mail.gmail.com>
Date:	Tue, 22 Sep 2015 14:41:50 +0800
From:	慕冬亮 <mudongliangabcd@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: [PATCH]Documentation: fix alignment

I don't find any maintainer in the MAINTAINERS who is in charge of
this document, so I post it to the lkml.

This patch is to fix alignment of one line in Documentation/security/LSM.txt

Signed-off-by: Dongliang Mu <mudongliangabcd@...il.com>
---

diff --git a/Documentation/security/LSM.txt b/Documentation/security/LSM.txt
index 3db7e67..9b37f5d 100644
--- a/Documentation/security/LSM.txt
+++ b/Documentation/security/LSM.txt
@@ -22,13 +22,13 @@ system, building their checks on top of the
defined capability hooks.
 For more details on capabilities, see capabilities(7) in the Linux
 man-pages project.

-Based on https://lkml.org/lkml/2007/10/26/215,
-a new LSM is accepted into the kernel when its intent (a description of
-what it tries to protect against and in what cases one would expect to
-use it) has been appropriately documented in Documentation/security/.
-This allows an LSM's code to be easily compared to its goals, and so
-that end users and distros can make a more informed decision about which
-LSMs suit their requirements.
+Based on https://lkml.org/lkml/2007/10/26/215, a new LSM is accepted
+into the kernel when its intent (a description of what it tries to
+protect against and in what cases one would expect to use it) has been
+appropriately documented in Documentation/security/. This allows an LSM's
+code to be easily compared to its goals, and so that end users and
+distros can make a more informed decision about which LSMs suit their
+requirements.

 For extensive documentation on the available LSM hook interfaces, please
 see include/linux/security.h.
 ---
--
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