python/semanage: Examples are no longer in the main semanage man page
PATCH 1/1 python/semanage: Examples are no longer in the main semanage man page
From: Dan Walsh <[email protected]>
Signed-off-by Petr Lautrbach <[email protected]>
--- python/semanage/semanage.8 | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-)
python/semanage/semanage.8 +2 -3
@@ -57,9 +57,8 @@ to SELinux user identities (which controls the initial security context assigned to Linux users when they login and bounds their authorized role set) as well as security context mappings for various kinds of objects, such as network ports, interfaces, infiniband pkeys and endports, and nodes (hosts) -as well as the file context mapping. See the EXAMPLES section below for some -examples of common usage. Note that the semanage login command deals with the -mapping from Linux usernames (logins) to SELinux user identities, +as well as the file context mapping. Note that the semanage login command deals +with the mapping from Linux usernames (logins) to SELinux user identities, while the semanage user command deals with the mapping from SELinux user identities to authorized role sets. In most cases, only the former mapping needs to be adjusted by the administrator; the latter
Signature · 1 line
2.20.1
Quoted 4 lines · Petr Lautrbach
From: Dan Walsh <[email protected]>
Signed-off-by Petr Lautrbach <[email protected]>
Indeed, commit 1925e1e91d99 ("Break the semanage man page into different man pages per category.") moved the examples in 2013.
Acked-by Nicolas Iooss <[email protected]>
Quoted 23 lines
--- python/semanage/semanage.8 | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-)python/semanage/semanage.8 +2
-4@@ -57,9 +57,8 @@ to SELinux user identities (which controls the initial security context assigned to Linux users when they login and bounds their authorized role set) as well as security context mappings for various kinds of objects, such as network ports, interfaces, infiniband pkeys and endports, and nodes (hosts) -as well as the file context mapping. See the EXAMPLES section below for some -examples of common usage. Note that the semanage login command deals with the -mapping from Linux usernames (logins) to SELinux user identities, +as well as the file context mapping. Note that the semanage login command deals +with the mapping from Linux usernames (logins) to SELinux user identities, while the semanage user command deals with the mapping from SELinux user identities to authorized role sets. In most cases, only the former mapping needs to be adjusted by the administrator; the latter --2.20.1
Quoted 11 lines · Nicolas Iooss
Quoted 4 lines · Petr Lautrbach
From: Dan Walsh <[email protected]>
Signed-off-by Petr Lautrbach <[email protected]>Indeed, commit
1925e1e91d99("Break the semanage man page into different man pages per category.") moved the examples in 2013.Acked-by Nicolas Iooss <[email protected]>
Merged. Thanks
Nicolas
Quoted 23 lines
Quoted 23 lines
--- python/semanage/semanage.8 | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-)python/semanage/semanage.8 +2
-4@@ -57,9 +57,8 @@ to SELinux user identities (which controls the initial security context assigned to Linux users when they login and bounds their authorized role set) as well as security context mappings for various kinds of objects, such as network ports, interfaces, infiniband pkeys and endports, and nodes (hosts) -as well as the file context mapping. See the EXAMPLES section below for some -examples of common usage. Note that the semanage login command deals with the -mapping from Linux usernames (logins) to SELinux user identities, +as well as the file context mapping. Note that the semanage login command deals +with the mapping from Linux usernames (logins) to SELinux user identities, while the semanage user command deals with the mapping from SELinux user identities to authorized role sets. In most cases, only the former mapping needs to be adjusted by the administrator; the latter --2.20.1