From: Xiaofeng Yan <xiaofeng.yan@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/1] dropbear: Change the path to find configuration file and add s configuration file for dropbear
Date: Mon, 29 Aug 2011 18:48:33 +0800 [thread overview]
Message-ID: <cover.1314604566.git.xiaofeng.yan@windriver.com> (raw)
From: Xiaofeng Yan <xiaofeng.yan@windriver.com>
dropbear will check "/etc/pam.d/sshd" which comes from package "openssh" \
When enabling pam supporting. But if we only install dropbear \
package without package "openssh", then "dropbear" will not \
find a configuration file. The changes are as follow for fixing this bug:
- Change the path to find configuration file (/etc/pam.d/sshd --> /etc/pam.d/dropbear)
- Add configuration file "/etc/pam.d/dropbear"
Pull URL: git://git.pokylinux.org/poky-contrib.git
Branch: xiaofeng/dropbear
Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=xiaofeng/dropbear
Thanks,
Xiaofeng Yan <xiaofeng.yan@windriver.com>
---
Xiaofeng Yan (1):
dropbear: Change the path to find configuration file and add a
configuration file for dropbear
meta/recipes-core/dropbear/dropbear.inc | 6 +++++-
meta/recipes-core/dropbear/dropbear/dropbear | 4 ++++
.../dropbear/dropbear-configuration-file.patch | 18 ++++++++++++++++++
3 files changed, 27 insertions(+), 1 deletions(-)
create mode 100644 meta/recipes-core/dropbear/dropbear/dropbear
create mode 100644 meta/recipes-core/dropbear/dropbear/dropbear-configuration-file.patch
next reply other threads:[~2011-08-29 10:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-29 10:48 Xiaofeng Yan [this message]
2011-08-29 10:48 ` [PATCH 1/1] dropbear: Change the path to find configuration file and add a configuration file for dropbear Xiaofeng Yan
2011-08-29 12:54 ` Richard Purdie
2011-08-31 2:13 ` Xiaofeng Yan
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=cover.1314604566.git.xiaofeng.yan@windriver.com \
--to=xiaofeng.yan@windriver.com \
--cc=openembedded-core@lists.openembedded.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