linux-kernel - [PATGCH -next] LSM: SafeSetID: fix underline length warning

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: <ac079c4a-a9ec-1a46-455a-035b8cf44d6f@infradead.org>
Date:   Sun, 23 Aug 2020 16:51:24 -0700
From:   Randy Dunlap <rdunlap@...radead.org>
To:     LKML <linux-kernel@...r.kernel.org>,
        "linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
        Thomas Cedeno <thomascedeno@...gle.com>,
        Micah Morton <mortonm@...omium.org>
Subject: [PATGCH -next] LSM: SafeSetID: fix underline length warning

From: Randy Dunlap <rdunlap@...radead.org>

Fix documentation build warning:

Documentation/admin-guide/LSM/SafeSetID.rst:110: WARNING: Title underline too short.
Note on GID policies and setgroups()
==================

Fixes: 02e316b088df ("LSM: SafeSetID: Add GID security policy handling")
Signed-off-by: Randy Dunlap <rdunlap@...radead.org>
Cc: Thomas Cedeno <thomascedeno@...gle.com>
Cc: Micah Morton <mortonm@...omium.org>
---
 Documentation/admin-guide/LSM/SafeSetID.rst |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

--- linux-next-20200821.orig/Documentation/admin-guide/LSM/SafeSetID.rst
+++ linux-next-20200821/Documentation/admin-guide/LSM/SafeSetID.rst
@@ -107,7 +107,7 @@ for a UID/GID will prevent that UID/GID
 privileges, such as allowing a user to set up user namespace UID/GID mappings.
 
 Note on GID policies and setgroups()
-==================
+====================================
 In v5.9 we are adding support for limiting CAP_SETGID privileges as was done
 previously for CAP_SETUID. However, for compatibility with common sandboxing
 related code conventions in userspace, we currently allow arbitrary