All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15847] New: Systemd: Incorrect Permission on /usr/lib/systemd
Date: Thu, 09 Nov 2023 11:07:14 +0000	[thread overview]
Message-ID: <bug-15847-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=15847

            Bug ID: 15847
           Summary: Systemd: Incorrect Permission on /usr/lib/systemd
           Product: buildroot
           Version: 2023.08.2
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: minor
          Priority: P5
         Component: Other
          Assignee: unassigned@buildroot.uclibc.org
          Reporter: justin.brown@fandingo.org
                CC: buildroot@uclibc.org
  Target Milestone: ---

I'm trying to use systemd as my init and systemd-networkd as my connection
manager. There appears to be a problem with the file permissions that prevent
networkd from starting. 


CONFIG:
=======

I'm tracking origin/master and am up to date with fd41e442f0f from Nov. 7th. My
defconfig is qemu_x86_64_defconfig with two modifications: BR2_INIT_SYSTEMD=y
(including BR2_PACKAGE_SYSTEMD_NETWORKD=y) and a BR2_ROOTFS_OVERLAY that
provides a etc/systemd/network/01.network basic DHCP unit file. (Plus the
additional both required and optional linux.config modifications for systemd
specified at https://github.com/systemd/systemd/blob/main/README.) 


PROBLEM:
========

The systemd package creates a systemd-network user, and the
systemd-networkd.service unit executes as that user. However, the file
permissions prohibit this non-root user from executing
/usr/lib/systemd/systemd-networkd:


# ls -ald /usr/lib/systemd/
drwxrwx---   13 root     root          2048 Nov  9 10:10 /usr/lib/systemd/

# ls -al /usr/lib/systemd/systemd-networkd
-rwxr-xr-x    1 root     root       1579456 Nov  9 10:10
/usr/lib/systemd/systemd-networkd


Note that the /usr/lib/systemd directory does not allow the necessary o=rx
permissions for a non-root user to access these binaries.


REQUEST:
========

I'm not well versed in writing makefiles, yet. But from a sh perspective, the
solution seems to be that the systemd package makefile needs to do the
equivalent of:

chmod o+rx /usr/lib/systemd

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

             reply	other threads:[~2023-11-09 11:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-09 11:07 bugzilla [this message]
2023-11-10 19:52 ` [Buildroot] [Bug 15847] Systemd: Incorrect Permission on /usr/lib/systemd bugzilla
2023-11-22  8:58 ` bugzilla
2024-06-15 15:13 ` bugzilla

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-15847-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@uclibc.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.