Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Xiaofeng Yan <xiaofeng.yan@windriver.com>
To: <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 10:13:18 +0800	[thread overview]
Message-ID: <4E5D98BE.7040401@windriver.com> (raw)
In-Reply-To: <1314622451.5939.285.camel@rex>

On 2011年08月29日 20:54, Richard Purdie wrote:
> On Mon, 2011-08-29 at 18: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            |    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
>>
>> diff --git a/meta/recipes-core/dropbear/dropbear.inc b/meta/recipes-core/dropbear/dropbear.inc
>> index 5af9ebd..577b288 100644
>> --- a/meta/recipes-core/dropbear/dropbear.inc
>> +++ b/meta/recipes-core/dropbear/dropbear.inc
>> @@ -19,7 +19,9 @@ SRC_URI = "http://matt.ucc.asn.au/dropbear/releases/dropbear-${PV}.tar.gz \
>>   	         file://init \
>>                    ${@base_contains('DISTRO_FEATURES', 'pam', '${PAM_SRC_URI}', '', d)} "
>>
>> -PAM_SRC_URI = "file://dropbear-enable-pam.patch"
>> +PAM_SRC_URI = "file://dropbear-enable-pam.patch \
>> +               file://dropbear-configuration-file.patch \
>> +               file://dropbear"
>>
>>   inherit autotools update-rc.d
>>
>> @@ -51,6 +53,7 @@ do_install() {
>>   		   ${D}${sysconfdir}/init.d \
>>   		   ${D}${sysconfdir}/default \
>>   		   ${D}${sysconfdir}/dropbear \
>> +		   ${D}${sysconfdir}/pam.d \
>>                      ${D}${bindir} \
>>   		   ${D}${sbindir} \
>>   		   ${D}${localstatedir}
>> @@ -68,6 +71,7 @@ do_install() {
>>   				  -e 's,/usr/bin,${bindir},g' \
>>   				  -e 's,/usr,${prefix},g'>  ${D}${sysconfdir}/init.d/dropbear
>>   	chmod 755 ${D}${sysconfdir}/init.d/dropbear
>> +	install -m 0644 ${WORKDIR}/dropbear  ${D}${sysconfdir}/pam.d/
> I suspect this won't build in the DISTRO_FEATURES not containing pam
> case due to the above file not existing. Please put a check in there to
> see if it exists.
>
Sorry for my fault. you are a really careful man. I will modify my fault.

Thanks
Yan
> Cheers,
>
> Richard
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>




  reply	other threads:[~2011-08-31  2:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-29 10:48 [PATCH 0/1] dropbear: Change the path to find configuration file and add s configuration file for dropbear 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 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-08-31  2:48 [PATCH 0/1] " Xiaofeng Yan
2011-08-31  2:48 ` [PATCH 1/1] " Xiaofeng Yan
2011-08-31 18:56   ` Richard Purdie

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=4E5D98BE.7040401@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