From: Daniel J Walsh <dwalsh@redhat.com>
To: Mikhail Efremov <mikhefr@gmail.com>
Cc: selinux@tycho.nsa.gov
Subject: Re: [PATCH] policycoreutils: newrole: Fix drop_capabilities().
Date: Fri, 16 Mar 2012 09:38:10 -0400 [thread overview]
Message-ID: <4F634242.6060400@redhat.com> (raw)
In-Reply-To: <20120316165040.1509ef42@c203.office.altlinux.ru>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 03/16/2012 08:50 AM, Mikhail Efremov wrote:
> Hello!
>
> The CAP_* constants should not be or'ed, it is the bit numbers. And
> grant the access to the audit system too.
>
> P.S. May be someone can look at the commit messages, I'm not sure
> about my English.
>
I talked to the developer of libcap-ng (Steve Grubb) and he stated
that you are correct but "you should use the 'v' version of update
which allows you to update in just 1 library call. The
capabilities should be separated with a comma and to mark the end you
put a -1:"
capng_updatev(CAPNG_ADD, CAPNG_EFFECTIVE | CAPNG_PERMITTED,
CAP_SYS_ADMIN,
CAP_FOWNER, CAP_CHOWN, CAP_DAC_OVERRIDE, CAP_SETPCAP, CAP_AUDIT_WRITE,
- -1);
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk9jQkIACgkQrlYvE4MpobPK7wCfbrheXgQ3P49ztISEAya3OzDM
cAEAoMNEw9qe2+csKVh4Vup5XauG8cXG
=DUox
-----END PGP SIGNATURE-----
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2012-03-16 13:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-16 12:50 [PATCH] policycoreutils: newrole: Fix drop_capabilities() Mikhail Efremov
2012-03-16 13:38 ` Daniel J Walsh [this message]
2012-03-16 14:30 ` Mikhail Efremov
2012-03-16 15:13 ` Daniel J Walsh
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=4F634242.6060400@redhat.com \
--to=dwalsh@redhat.com \
--cc=mikhefr@gmail.com \
--cc=selinux@tycho.nsa.gov \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.