From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] simple question about dropbear
Date: Tue, 14 Feb 2012 10:55:01 +0100 [thread overview]
Message-ID: <87aa4lwxhm.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <BAB70BB3-C317-49C7-80E2-016DD9BECAF1@informatik.uni-bremen.de> (Johannes Teiwes's message of "Tue, 14 Feb 2012 10:30:45 +0100")
>>>>> "Johannes" == Johannes Teiwes <jteiwes@informatik.uni-bremen.de> writes:
Hi,
Johannes> I have also BR2_PACKAGE_DROPBEAR_SMALL enabled in my
Johannes> configuration. The 'slowness' can be the cause since the
Johannes> microblaze machine only runs at about 66MHz.
Johannes> Is there any way to convince dropbear/ssh to use a small (or
Johannes> precomputed) session key? If this is possible one could
Johannes> check, if the system-speed is really the limiting factor.
Not afaik. You could try disabling DROPBEAR_SMALL and rebuild dropbear
(rm -rf output/build/dropbear-*; make)
Johannes> I am using static device tables and the default dev_table as
Johannes> my structure - maybe there are some devices missing or
Johannes> misconfigured for doing ssh right out of the box?
No, it should afaik work out of the box. Does it put anything sensible
in /var/log/messages?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2012-02-14 9:55 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
[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 [this message]
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=87aa4lwxhm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox