Dropbear 0.44test4 problems

[Razzle]

Dropbear refuses to establish ssh connections for me..
When I try to connect I get either  "No auth methods could be used." (RSAKeyAuthentication only machine) or "bad buf_getwriteptr".

Why does OZ 3.5.1 use dropbear instead of openssh?

[Mickeyl]

size.

[Razzle]

if smaller size means unstable, I'll choose choose stability over size..

[Teletubbie]

Hi,
there is just not enough place on root filesystem to put ssh in. We tried a lot, for example combining dropbear with some components of the openssh package. No chance. There still is hope for the 3.6 release that will be based on ulibc. Then there will maybe be enough place...
You can also shift your root file system to card then replace dropbear.
Cheers,
Sam

[Razzle]

Hi,
there is just not enough place on root filesystem to put ssh in. We tried a lot, for example combining dropbear with some components of the openssh package. No chance. There still is hope for the 3.6 release that will be based on ulibc. Then there will maybe be enough place...
You can also shift your root file system to card then replace dropbear.
Cheers,
Sam

Ok then I will either hope for this or maybe find a solution for my problems.

Or am I the only one getting errors with dropbear?

[Teletubbie]

Hi again,
please think about shifting parts of the root file system to card. For me this is something that helps to get out of a lot of problems.
First you will need a (better a fast) card. I use an SD card so I a can use the CF Slot for Wifi. For SD cards be carefull, not all will work with the Zaurus. I am using a panasonic high speed 256MB card. Maybe you get also the fast SD Driver:
http://www.zaurususergroup.com/UpDownload+...ad-sid-52.phtml
(I dont know if this driver is now included in 3.5.1 or not)
Then you can do this:
1) http://www.linux-migration.org/ch05s10s05s02.html
2) http://www.linux-migration.org/ch05s10s05s03.html
3) http://www.linux-migration.org/ch05s10s05s04.html
4) http://www.linux-migration.org/ch05s10s05s05.html

(There is no usr/local on zaurus so change:
for d in local share; do
to:
for d in share; do

5) reboot

This is the procedure I always do. Now you should have enough memory. In this case you can also now use a 58/6 or 64/0 Kernel to have more ram for performance, since now everything is now linked to card if you just install them to root and you dont need to install things to ram anymore.
After this all you can now uninstall dropbear and install the whole openssh package from here:
http://www.openzaurus.org/official/unstable/3.5.1/upgrades/

Well this is a little bit advanced zaurus user but using openzaurus is also a little bit advanced. So if you have questions about this thing, feel free to ask.
Have fun,
Sam

[Mickeyl]

The other possibility would be to take part in the open source process, i.e. start debugging what happens with dropbear compared to openssh and when you found the bug, make a patch and submit it to the dropbear folks...

[Razzle]

Thank you both for your input  

I could not yet decide what to do. Either the easy way or the (more interesting) hard way.
Can you give me some links on debugging on the Z?
I'll probably use Teletubbie's suggestion for now due to lack of time for more but a fix is always better than a workaround.

[Mickeyl]

Actually I wouldn't debug this situation on the Z first. First I would check if the same happens w/ dropbear-0.44test on a x86 PC, where you can step through the code etc.

If the PC exposes the same behaviour, then you need to find out which code doesn't work and fix that. If only the Z exposes the problem, then you need to build debugging images for the Z and use gdb to step through the code on the Z.