From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] dropbear: Change the path to find configuration file and add a configuration file for dropbear
Date: Wed, 31 Aug 2011 19:56:26 +0100 [thread overview]
Message-ID: <1314816986.5939.478.camel@rex> (raw)
In-Reply-To: <44d5fd558b4079edf813e96ff0bf6ce06930c0dd.1314758474.git.xiaofeng.yan@windriver.com>
On Wed, 2011-08-31 at 10:48 +0800, Xiaofeng Yan wrote:
> 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 a configuration file "/etc/pam.d/dropbear"
>
> Signed-off-by: Xiaofeng Yan <xiaofeng.yan@windriver.com>
> ---
> meta/recipes-core/dropbear/dropbear.inc | 12 +++++++++++-
> 1 files changed, 11 insertions(+), 1 deletions(-)
Merged to master, thanks.
Richard
next prev parent reply other threads:[~2011-08-31 19:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-31 2:48 [PATCH 0/1] dropbear: Change the path to find configuration file and add a configuration file for dropbear Xiaofeng Yan
2011-08-31 2:48 ` [PATCH 1/1] " Xiaofeng Yan
2011-08-31 18:56 ` Richard Purdie [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-08-29 10:48 [PATCH 0/1] dropbear: Change the path to find configuration file and add s " Xiaofeng Yan
2011-08-29 10:48 ` [PATCH 1/1] dropbear: Change the path to find configuration file and add a " 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=1314816986.5939.478.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--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