Many thanks for this suggestion. I appreciate the advantages of
capabilities support.
Openrc also has optional capabilities support in supervise-daemon which might be
an advantage to users, but isn't used by default in Debian.
It might be worth exploring adding capabilities support to src:dpkg start-stop-daemon. Maybe the src:openrc code would be a starting point. I haven't looked how much the two codebases have diverged.
Guillem,
What do you think?
On Wed, 28 Jun 2023 01:57:27 +0200
Guillem Jover <guillem@debian.org> wrote:
Some time ago I asked on d-d whether anyone would have an issue with dpkg.deb in Debian linking against libcap [D]. And where I had worked
on the following branch:
https://git.hadrons.org/git/debian/dpkg/dpkg.git/log/?h=next/s-s-d-posix-caps
Which I need to go over again before merging. But otherwise support
for this in that or some other similar form should be coming soon to
s-s-d.
I had a quick look at the branch you posted and I'm not sure it
overlaps with the feature requested with this bug.
If I understand --dropcap correctly it is meant to remove capabilities
from the daemon started by s-s-d, correct?
What I am looking for is quite the opposite, however. I'm looking for a
way to add new capabilities to the ambient set of the started daemon.
The ambient set is important for daemons written in interpreted
languages where capabilities cannot be set on the executable file and
where the language may not provide a means to manipulate capabilities
itself.
In such cases, s-s-d would need to set up the capabilities for the
daemon prior to it being exec'ed.
Also I would favour if OpenRC's and dpkg's start-stop-daemon could try
to share a common interface. This would make life easier for init
script writers.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 300 |
Nodes: | 16 (2 / 14) |
Uptime: | 46:36:47 |
Calls: | 6,710 |
Calls today: | 3 |
Files: | 12,243 |
Messages: | 5,354,357 |
Posted today: | 1 |