linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Mayo <aklhfex-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
	linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [patch] capabilities.7: NOTES: add last kernel versions for obsolete options
Date: Sun, 16 Nov 2014 17:03:38 +0000	[thread overview]
Message-ID: <5468D8EA.9070102@gmail.com> (raw)


CONFIG_SECURITY_CAPABILITIES option removed by:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/security?id=5915eb53861c5776cfec33ca4fcc1fd20d66dd27

CONFIG_SECURITY_FILE_CAPABILITIES option removed in Linux 2.6.33 as already mentioned in DESCRIPTION

Signed-off-by: Chris Mayo <aklhfex-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
---
 man7/capabilities.7 | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/man7/capabilities.7 b/man7/capabilities.7
index a1adcb5..bc461a4 100644
--- a/man7/capabilities.7
+++ b/man7/capabilities.7
@@ -1124,7 +1124,7 @@ is based on the withdrawn POSIX.1e draft standard; see
 .UR http://wt.tuxomania.net\:/publications\:/posix.1e/
 .UE .
 .SH NOTES
-Since kernel 2.5.27, capabilities are an optional kernel component,
+From kernel 2.5.27 to kernel 2.6.26, capabilities are an optional kernel component,
 and can be enabled/disabled via the
 .B CONFIG_SECURITY_CAPABILITIES
 kernel configuration option.
@@ -1161,7 +1161,7 @@ It can be found at
 .UR http://www.kernel.org\:/pub\:/linux\:/libs\:/security\:/linux-privs
 .UE .
 
-Before kernel 2.6.24, and since kernel 2.6.24 if
+Before kernel 2.6.24, and from kernel 2.6.24 to kernel 2.6.32 if
 file capabilities are not enabled, a thread with the
 .B CAP_SETPCAP
 capability can manipulate the capabilities of threads other than itself.
-- 
2.0.4

--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2014-11-16 17:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-16 17:03 Chris Mayo [this message]
     [not found] ` <5468D8EA.9070102-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-02-05 14:17   ` [patch] capabilities.7: NOTES: add last kernel versions for obsolete options Michael Kerrisk (man-pages)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5468D8EA.9070102@gmail.com \
    --to=aklhfex-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).