setpriv: improve securebits list formatting in man page

Signed-off-by: Karel Zak <kzak@redhat.com>

diff --git a/sys-utils/setpriv.1.adoc b/sys-utils/setpriv.1.adoc
index b96e83fb9157be0b028f090a5c84df2d863e82f9..e67a23454ad679a397c32905503b094eaa67001e 100644 (file)
--- a/sys-utils/setpriv.1.adoc
+++ b/sys-utils/setpriv.1.adoc
@@ -74,7 +74,20 @@ Setting a _uid_ or _gid_ does not change capabilities, although the exec call at
 *setpriv --reuid=1000 --regid=1000 --inh-caps=-all*
 
 *--securebits* (**+**|*-*)__securebit__...::
-Set or clear securebits. The argument is a comma-separated list. The valid securebits are _noroot_, _noroot_locked_, _no_setuid_fixup_, _no_setuid_fixup_locked_, _keep_caps_locked_, _no_cap_ambient_raise_, _no_cap_ambient_raise_locked_, _exec_restrict_file_, _exec_restrict_file_locked_, _exec_deny_interactive_, and _exec_deny_interactive_locked_. _keep_caps_ is cleared by *execve*(2) and is therefore not allowed.
+Set or clear securebits. The argument is a comma-separated list.
+The valid securebits are:
++
+* _noroot_
+* _noroot_locked_
+* _no_setuid_fixup_
+* _no_setuid_fixup_locked_
+* _keep_caps_locked_ (_keep_caps_ is cleared by *execve*(2) and is therefore not allowed)
+* _no_cap_ambient_raise_
+* _no_cap_ambient_raise_locked_
+* _exec_restrict_file_
+* _exec_restrict_file_locked_
+* _exec_deny_interactive_
+* _exec_deny_interactive_locked_
 
 **--pdeathsig keep**|**clear**|*<signal>*::
 Keep, clear or set the parent death signal. Some LSMs, most notably SELinux and AppArmor, clear the signal when the process' credentials change. Using *--pdeathsig keep* will restore the parent death signal after changing credentials to remedy that situation.