All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: Conflicting providers for ssh/sshd (dropbear and	openssh)
Date: Tue, 28 Jun 2011 18:07:22 -0700	[thread overview]
Message-ID: <4E0A7ACA.90004@gmail.com> (raw)
In-Reply-To: <4E0A6995.1040006@slimlogic.co.uk>

On 06/28/2011 04:53 PM, Graeme Gregory wrote:
> On 06/29/2011 12:50 AM, Khem Raj wrote:
>>
>> On Jun 28, 2011, at 3:51 PM, Scott Garman<scott.a.garman@intel.com>  wrote:
>>
>>> On 06/28/2011 03:41 PM, Khem Raj wrote:
>>>> ERROR: Multiple .bb files are due to be built which each provide ssh
>>>> (/home/kraj/work/angstrom/sources/openembedded-core/meta/recipes-core/dropbear/dropbear_0.52.bb
>>>> /home/kraj/work/angstrom/sources/openembedded-core/meta/recipes-connectivity/openssh/openssh_5.8p2.bb).
>>>>   This usually means one provides something the other doesn't and should.
>>>> ERROR: Multiple .bb files are due to be built which each provide sshd
>>>> (/home/kraj/work/angstrom/sources/openembedded-core/meta/recipes-core/dropbear/dropbear_0.52.bb
>>>> /home/kraj/work/angstrom/sources/openembedded-core/meta/recipes-connectivity/openssh/openssh_5.8p2.bb).
>>>>   This usually means one provides something the other doesn't and should.
>>>>
>>>> reason is that dropbear only provides ssh and sshd packages openssh
>>>> provides a few more e.g. openssh-sftp-server which is demanded by
>>>> some images and at same time wants dropbear to provide sshd and ssh
>>>>
>>>> Now both recipes are to be built but are in contention for providing
>>>> ssh and sshd
>>>>
>>>> How to solve this problem. ? Are other packages that openssh provides
>>>> strictly depending on ssh/sshd from openssh ? or will they work on
>>>> any ssh/sshd ?
>>>>
>>>> If they are independent then may be the openssh recipe should be
>>>> divided into openssh-ssh and openssh-rest so one can use openssh
>>>> provided daemon or dropbear provided as they wish
>>> I've run into that and have been wondering how to resolve it as well.
>>>
>>> If there are currently existing images which are pulling in dropbear's ssh and sshd while using openssh's sftp-server, then that would imply they can work independently, even though that combo seems like an aggressive space optimization that I would tend to avoid.
>> yes if you build console-image with angstrom you will see it wanting sftp-server and dr bear for rest of ssh needs
>>
> sftp-server is just a really small ftp like program that gets run as the
> shell when sftp connects instead of ssh. It has no dependency on any
> openssh code or even openssl.

ok that solves my question about deps on ssh/ssh from openssh. So it 
seems we can refactor the openssh recipe


  This is the reason why the dropbear
> developer decided to just use it instead of writing his own exact work
> alike.
>
> I was the one that added it to Angstrom images as I really like to sftp
> out of the box.
>
> Graeme
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core




  reply	other threads:[~2011-06-29  1:11 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-28 22:41 Conflicting providers for ssh/sshd (dropbear and openssh) Khem Raj
2011-06-28 22:51 ` Scott Garman
2011-06-28 23:50   ` Khem Raj
2011-06-28 23:53     ` Graeme Gregory
2011-06-29  1:07       ` Khem Raj [this message]
2011-06-29  7:42   ` Anders Darander
2011-06-29  0:34 ` Scott Garman
2011-06-29  8:24 ` Koen Kooi
2011-06-29  8:50   ` Anders Darander
2011-06-29  8:56     ` Koen Kooi
2011-06-29  9:08       ` Phil Blundell
2011-06-29  9:42         ` Richard Purdie
2011-06-29  9:51           ` Phil Blundell
2011-06-29 10:23             ` Richard Purdie
2011-06-29  9:13       ` Anders Darander
2011-06-29 17:03       ` Scott Garman
2011-07-03 12:26       ` Philip Balister
2011-07-03 15:41         ` Graeme Gregory
2011-06-29  8:56     ` Graeme Gregory

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=4E0A7ACA.90004@gmail.com \
    --to=raj.khem@gmail.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 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.