From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15838] New: dhcp server creates symlinks to /tmp on host
Date: Wed, 01 Nov 2023 22:01:07 +0000 [thread overview]
Message-ID: <bug-15838-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=15838
Bug ID: 15838
Summary: dhcp server creates symlinks to /tmp on host
Product: buildroot
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned@buildroot.uclibc.org
Reporter: jonas.d.karlsson@gmail.com
CC: buildroot@uclibc.org
Target Milestone: ---
In package/dhcp/dhcp.mk this section can be found:
ifeq ($(BR2_PACKAGE_DHCP_SERVER),y)
define DHCP_INSTALL_CTL_LIBS
$(MAKE) -C $(@D)/dhcpctl install-exec DESTDIR=$(TARGET_DIR)
endef
define DHCP_INSTALL_SERVER
mkdir -p $(TARGET_DIR)/var/lib
(cd $(TARGET_DIR)/var/lib; ln -snf /tmp dhcp)
$(MAKE) -C $(@D)/server DESTDIR=$(TARGET_DIR) install-sbinPROGRAMS
$(INSTALL) -m 0644 -D package/dhcp/dhcpd.conf \
$(TARGET_DIR)/etc/dhcp/dhcpd.conf
endef
endif
The symlink that is created from /var/lib/dhcp to /tmp seem to cause a symlink
to the host /tmp which creates access privilege problems.
Shouldn't the symlink be to ../../tmp rather than /tmp like the misc symlink
under /var/lib? See below
cd output/target/var/lib
ls -al
drwxr-xr-x 2 jonkar jonkar 4096 nov 1 17:09 arpd
lrwxrwxrwx 1 jonkar jonkar 4 nov 1 18:27 dhcp -> /tmp
lrwxrwxrwx 1 jonkar jonkar 9 nov 1 16:13 misc -> ../../tmp
--
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
next reply other threads:[~2023-11-01 22:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-01 22:01 bugzilla [this message]
2024-06-15 15:13 ` [Buildroot] [Bug 15838] dhcp server creates symlinks to /tmp on host 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-15838-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox