All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-man@vger.kernel.org
Subject: [Bug 216667] Self-contradictory description of inheritable capability set
Date: Fri, 19 May 2023 02:28:13 +0000	[thread overview]
Message-ID: <bug-216667-11311-2jwcSW44IY@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216667-11311@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=216667

--- Comment #2 from Monthero Ronald (rhmcruiser@gmail.com) ---
If curious you can also check the process capabilities set and decode their
capabilities set flags for -  permitted, inherited and ambient as below.
The capabilities set can differ based on process , user and privileges 

Example:

test$ ps alx | grep docker 
4     0    2068       1  20   0 1834532 76808 -     Ssl  ?          0:16
/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock
0  1000   70187   65976  20   0  17868  2504 pipe_r S+   pts/7      0:00 grep
--color=auto docker
test$ 
test$ egrep Cap  /proc/2068/status 
CapInh: 0000000000000000
CapPrm: 000001ffffffffff
CapEff: 000001ffffffffff
CapBnd: 000001ffffffffff
CapAmb: 0000000000000000
test$ 

Decode the capability flags for this process

test$ capsh --decode=000001ffffffffff
0x000001ffffffffff=cap_chown,cap_dac_override,cap_dac_read_search,cap_fowner,cap_fsetid,cap_kill,cap_setgid,cap_setuid,cap_setpcap,cap_linux_immutable,cap_net_bind_service,cap_net_broadcast,cap_net_admin,cap_net_raw,cap_ipc_lock,cap_ipc_owner,cap_sys_module,cap_sys_rawio,cap_sys_chroot,cap_sys_ptrace,cap_sys_pacct,cap_sys_admin,cap_sys_boot,cap_sys_nice,cap_sys_resource,cap_sys_time,cap_sys_tty_config,cap_mknod,cap_lease,cap_audit_write,cap_audit_control,cap_setfcap,cap_mac_override,cap_mac_admin,cap_syslog,cap_wake_alarm,cap_block_suspend,cap_audit_read,cap_perfmon,cap_bpf,cap_checkpoint_restore
test$

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2023-05-19  2:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-06  3:04 [Bug 216667] New: Self-contradictory description of inheritable capability set bugzilla-daemon
2023-05-19  2:11 ` [Bug 216667] " bugzilla-daemon
2023-05-19  2:28 ` bugzilla-daemon [this message]
2023-05-19 13:26 ` bugzilla-daemon
2023-05-19 13:26 ` bugzilla-daemon
2023-05-25  0:55 ` bugzilla-daemon

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=bug-216667-11311-2jwcSW44IY@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linux-man@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 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.