linux-kernel - suggestion: msgctl(IPC_RMID) req CAP_IPC_OWNER instead of CAP_SYS

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-Id: <6.2.5.6.2.20100102005433.03a07f40@flumedata.com>
Date:	Sat, 02 Jan 2010 01:01:05 -0500
From:	starlight@...nacle.cx
To:	linux-kernel@...r.kernel.org
Subject: suggestion:  msgctl(IPC_RMID) req CAP_IPC_OWNER instead
  of CAP_SYS_ADMIN

Hello,

We have a service daemon that must on occasion clean up orphaned 
SVR4/POSIX message queues left over by dead client processes.

The service daemon runs with least privileges, and it receives a 
small set of capabilities that its job demands.

However I was surprised to see that CAP_SYS_ADMIN is needed when
using IPC_RMID to remove message queues owned by other user 
IDs.  This is a powerful and dangerous privilege and I dislike 
assigning it to the daemon.  Seems to me that CAP_IPC_OWNER is a 
better fit for this function.

This is just a suggestion.  Please respond with my e-mail CCed 
as I am not a list subscriber.

Regards

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/