Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Andre McCurdy <armccurdy@gmail.com>, Khem Raj <raj.khem@gmail.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] dropbear: drop obsolete patch 0004-fix-2kb-keys.patch
Date: Tue, 29 May 2018 19:56:16 +0100	[thread overview]
Message-ID: <1527620176.16911.114.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAJ86T=XdWPKG+EURX35cgpxbOL6FetzKdoND+=aXte1MPcxdtw@mail.gmail.com>

On Tue, 2018-05-29 at 11:26 -0700, Andre McCurdy wrote:
> On Tue, May 29, 2018 at 10:29 AM, Khem Raj <raj.khem@gmail.com>
> wrote:
> > 
> > On Thu, May 24, 2018 at 7:27 PM, Andre McCurdy <armccurdy@gmail.com
> > > wrote:
> > > 
> > > This patch has been obsolete since 2005:
> > > 
> > >   https://github.com/mkj/dropbear/commit/736f370dce614b717193f45d
> > > 084e9e009de723ce
> > Seems fine to drop but I would like to understand why we carried it
> > thus far.
> > What is the history of it in OE ?
> It's older than the git history in oe-core (ie it was added in August
> 2005 as part of the first commit to oe-core).
> 
> The patch looks like it was initially created in March 2005 against
> dropbear 0.45.
> 
> In 2011 someone (incorrectly) added a tag "Upstream-Status:
> Inappropriate [configuration]".
> 
> That's about as much history as we have.

Looks like it was added for 0.44:

http://git.openembedded.org/openembedded/commit/packages/dropbear?id=ed6e40d6aff6cffabeff6f7fd6a9fee062566b2c

and there was some associated discussion:

http://familiar.handhelds.narkive.com/b1VGg2bI/problem-w-dropbear-ssh

so remote systems with 2048 length keys were somehow causing it
problems?

Cheers,

Richard


  reply	other threads:[~2018-05-29 18:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-25  2:27 [PATCH] dropbear: drop obsolete patch 0004-fix-2kb-keys.patch Andre McCurdy
2018-05-29 17:29 ` Khem Raj
2018-05-29 18:26   ` Andre McCurdy
2018-05-29 18:56     ` Richard Purdie [this message]
2018-05-29 19:09       ` Andre McCurdy
2018-05-29 20:19         ` 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=1527620176.16911.114.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=armccurdy@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    /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