From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 8276] New: package/dropbear: symlink resolution incorrect
Date: Tue, 11 Aug 2015 01:49:53 +0000 (UTC) [thread overview]
Message-ID: <bug-8276-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=8276
Summary: package/dropbear: symlink resolution incorrect
Product: buildroot
Version: unspecified
Platform: All
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: nospam+busybox at jtang.org
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Commit 6dc5c7ff changed how the /etc/dropbear symlink is detected, by using
readlink to resolve the target location. When using coreutils's readlink,
"readlink -f /etc/dropbear" will return /var/run/dropbear. However, if using
busybox's readlink, the same "readlink -f /etc/dropbear" returns an empty
string. I am not sure if this is a bug in the /etc/init.d/S50dropbear script,
or if busybox is not honoring the "-f" flag.
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2015-08-11 1:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-11 1:49 bugzilla at busybox.net [this message]
2015-08-11 8:57 ` [Buildroot] [Bug 8276] package/dropbear: symlink resolution incorrect bugzilla at busybox.net
2015-08-11 9:09 ` bugzilla at busybox.net
2015-08-11 11:18 ` bugzilla at busybox.net
2015-08-11 22:43 ` bugzilla at busybox.net
2015-08-17 16:02 ` bugzilla at busybox.net
2015-08-18 2:12 ` bugzilla at busybox.net
2015-08-24 20:13 ` bugzilla at busybox.net
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-8276-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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 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.