From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] package/dbusbroker: new package
Date: Mon, 15 Jun 2020 12:21:19 +0200 [thread overview]
Message-ID: <20200615102119.GY2346@scaer> (raw)
In-Reply-To: <CADYdroPBJBr4psh4YLM+Er--SEF_1hCUd0Drqizcv3mjM2+eJw@mail.gmail.com>
Norbert, All,
On 2020-06-14 23:30 +0200, Norbert Lange spake thusly:
> Am So., 14. Juni 2020 um 15:10 Uhr schrieb Yann E. MORIN
> <yann.morin.1998@free.fr>:
[--SNIP--]
> > So you are very welcome to have re-spun this new iteration. :-)
> As said, I have trouble with the ML flow, seems like the commit should then
> include the whole discussion as otherwise no one is able to follow?
I guess that's what the post-commit history (all that is after the ---
line) is for: keep a track of the changes between the various iteration
of a patch (if I understood your isue correctly).
[--SNIP--]
> > OK, I knew that would have been systemd doing the uid-drop, by I'd still
> > like the info appear somewhere (so that we do not later question this in
> > light of the original dbus package which defines one).
> Not sure if we got some communication issues. The setting does
> something (drop privileges),
> while I originally considered the launcher ignoring the Xml key.
> I guess you could tweak the systemd service to use a Dynamic user,
> but I won't touch that for now.
So I did some testing:
- without the <user> entry in system.conf, the launcher and the
message bus are running as root.
- with a <user> entry in system.conf (and the correct user in
/etc/passwd and /etc/group), the launcher and the message bus are
running as non-root with the specified user, and systemd is working
happily.
So, I would like we do use a non-root user for dbus-broker, like we do
for the original dbus.
I'll add that when I re-submit later tonight.
[--SNIP--]
> > And explain in the commit log that the launcher needs systemd, and that
> > without the launcher there is no point in dbus-broker.
> Seems to be the best option for now IMHO. Revisit the launcher-less option
> once you have something to test.
Agreed.
[--SNIP--]
> dbus/broker should be enabled by default with systemd, but with some way
> that the user still can disable those. Dunno what's the correct to do
> this in buildroot,
> add a line to dbus 'default y if BR2_PACKAGE_SYSTEMD'?
We can revisit that in a later patch (I've seen and started to apply
your otehr series, which conclusion is to indeed drop the dbus
requirement; let's see that happen there, not here).
[--SNIP--]
> > If you agree, then I'll try to merge your new submission with your
> > comments into my series and re-spin it soon-ish, if that's OK with you.
> You doing the work, and I get to nag? Deal ;)
My pleasure! ;-)
Thanks for the discusion and the explanations. New iteration pending by
the end of the day (hopefully).
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
prev parent reply other threads:[~2020-06-15 10:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-10 23:24 [Buildroot] [PATCH v2] package/dbusbroker: new package Norbert Lange
2020-06-12 5:31 ` Yann E. MORIN
2020-06-12 7:02 ` Norbert Lange
2020-06-14 13:10 ` Yann E. MORIN
2020-06-14 21:30 ` Norbert Lange
2020-06-15 10:21 ` Yann E. MORIN [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=20200615102119.GY2346@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/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