From: Ravi kumar Veeramally <ravikumar.veeramally@linux.intel.com>
To: linux-bluetooth@vger.kernel.org
Cc: Ravi kumar Veeramally <ravikumar.veeramally@linux.intel.com>
Subject: [PATCH_v4 6/6] android: Add reasons for adding capabilites to process
Date: Fri, 29 Nov 2013 15:12:36 +0200 [thread overview]
Message-ID: <1385730756-32400-7-git-send-email-ravikumar.veeramally@linux.intel.com> (raw)
In-Reply-To: <1385730756-32400-1-git-send-email-ravikumar.veeramally@linux.intel.com>
CAP_NET_ADMIN: Allow use of MGMT interface
CAP_NET_BIND_SERVICE: Allow use of privileged PSM
CAP_NET_RAW: Allow use of bnep ioctl calls
---
android/main.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/android/main.c b/android/main.c
index 3a14af5..eedca58 100644
--- a/android/main.c
+++ b/android/main.c
@@ -534,6 +534,9 @@ static bool set_capabilities(void)
header.version = _LINUX_CAPABILITY_VERSION;
header.pid = 0;
+ /* CAP_NET_ADMIN: Allow use of MGMT interface
+ * CAP_NET_BIND_SERVICE: Allow use of privileged PSM
+ * CAP_NET_RAW: Allow use of bnep ioctl calls */
cap.effective = cap.permitted =
CAP_TO_MASK(CAP_NET_RAW) |
CAP_TO_MASK(CAP_NET_ADMIN) |
--
1.8.3.2
prev parent reply other threads:[~2013-11-29 13:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-29 13:12 [PATCH_v4 0/6] Refactor bnep code and implement pan methods Ravi kumar Veeramally
2013-11-29 13:12 ` [PATCH_v4 1/6] profiles/network: Refactor bnep connection setup functionality Ravi kumar Veeramally
2013-11-29 13:12 ` [PATCH_v4 2/6] profiles/network: Rename common.c|h to bnep.c|h Ravi kumar Veeramally
2013-11-29 13:12 ` [PATCH_v4 3/6] android/pan: Implement pan connect method in daemon Ravi kumar Veeramally
2013-11-29 13:12 ` [PATCH_v4 4/6] android/pan: Implement pan disconnect " Ravi kumar Veeramally
2013-11-29 13:12 ` [PATCH_v4 5/6] android/pan: Implement the get local role " Ravi kumar Veeramally
2013-11-29 13:12 ` Ravi kumar Veeramally [this message]
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=1385730756-32400-7-git-send-email-ravikumar.veeramally@linux.intel.com \
--to=ravikumar.veeramally@linux.intel.com \
--cc=linux-bluetooth@vger.kernel.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).