From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 6326] New: Dropbear: Add options to allow better config for different target devices (e.g. routers)
Date: Sat, 22 Jun 2013 21:23:56 +0000 (UTC) [thread overview]
Message-ID: <bug-6326-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=6326
Host: any
Target: any
Build: buildroot 2013.05
Summary: Dropbear: Add options to allow better config for
different target devices (e.g. routers)
Product: buildroot
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Keywords: patch
Severity: enhancement
Priority: P3
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: mail at maddes.net
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Created attachment 4952
--> https://bugs.busybox.net/attachment.cgi?id=4952
Patch (-p1) to add more buildroot options for Dropbear package.
Multiple embedded devices targets do not allow to put files everywhere,
therefore paths and commands must be adopted to the given file system.
Additionally the current make file changes the path of the xauth command in the
background instead of providing an config option.
The attached patch (-p1) adds four buildroot options to the Dropbear package,
so it's config can be adopted to any given situation.
Please apply for a future release.
Kind regards
Maddes
P.S.:
Bugzilla does not know the current stable release of buildroot.
--
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:[~2013-06-22 21:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-22 21:23 bugzilla at busybox.net [this message]
2013-06-23 1:57 ` [Buildroot] [Bug 6326] Dropbear: Add options to allow better config for different target devices (e.g. routers) bugzilla at busybox.net
2013-06-23 10:26 ` bugzilla at busybox.net
2013-06-23 17:35 ` 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-6326-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox