From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] simple question about dropbear
Date: Mon, 13 Feb 2012 21:38:39 +0100 [thread overview]
Message-ID: <87zkcmwjsg.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <CA+appbOjdSO6HqBNCALy_SmfkKycJNV_gHJqxY1aQbfyQbXMdg@mail.gmail.com> (Spenser Gilliland's message of "Mon, 13 Feb 2012 12:53:06 -0600")
>>>>> "Spenser" == Spenser Gilliland <spenser309@gmail.com> writes:
Spenser> Johannes,
Spenser> I'm having a similar issue with dropbear and have switched to the
Spenser> openssh server for now. What patches are you using for microblaze
Spenser> strace? I'd like to add them to my build.
So it might be a microblaze specific issue? This is Microblaze with mmu,
right?
Spenser> debug1: sending SSH2_MSG_KEXDH_INIT
Spenser> debug1: expecting SSH2_MSG_KEXDH_REPLY
This is afaik here were it generates the session key. Are you sure it
isn't just slow? Do you have BR2_PACKAGE_DROPBEAR_SMALL enabled?
There recently was some discussion about it on the dropbear list:
http://thread.gmane.org/gmane.network.ssh.dropbear/1018
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2012-02-13 20:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 9:01 [Buildroot] simple question about dropbear Johannes Teiwes
2012-02-10 10:44 ` Peter Korsgaard
2012-02-13 12:43 ` Johannes Teiwes
2012-02-13 18:53 ` Spenser Gilliland
2012-02-13 20:38 ` Peter Korsgaard [this message]
[not found] ` <47fbadb0-0be9-4cde-a2f0-8cef38742e89@email.android.com>
[not found] ` <CA+appbPMZ7iB6gXCuA4r7y_7Nj-AOoLghLAo-HEp6zzLavSa9A@mail.gmail.com>
2012-02-13 21:31 ` Peter Korsgaard
2012-02-13 23:56 ` Spenser Gilliland
2012-02-14 7:49 ` Peter Korsgaard
2012-02-14 9:30 ` Johannes Teiwes
2012-02-14 9:55 ` Peter Korsgaard
2012-02-14 10:59 ` Johannes Teiwes
2012-02-14 8:55 ` Johannes Teiwes
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=87zkcmwjsg.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.net \
/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.