Bela,
I received your new dropbear.tcz for raspberrypi. I installed it on rpi, and started, as you note, and as usually the parctice with this system daemons, use the start/stop script in ./init.d dir (the special is here, it is not in /etc, but in /usr/local/etc...):
sudo /usr/local/etc/init.d/dropbear start
It start and generate the key files, and listen on the ssh port.
To connect into it from a remote machine, need to create "standard" user(s) on rpi, means username with valid passwd. The recently used TC system has the default username tc, without any password, and this user has root privilegies. The ssh dont allow to make connection with username, havenot passwd.
Another small trick: when I tried to make connection on second time, start a bare/minimal tc system, the ssh dont allow me to make this connection. It happens, because on the previous session the runing dropbear sent me keys, and it was stored on the "remote" machine.
There is a "brute-force" solution to this situation: if you rename/delete the known.hosts file in your home dir, under ./.ssh, the dropbear daemon will send you new keys, valid for the new sessions.
You can see this on the attached screenshot: in the left-side terminal windows I made an ssh connection on my LAN, used the 192.168.1.111 ip. Previously you can see the rename of the known.hosts file. On the right-side windows I made connnection to the raspberrypi through my public ip address, hg5apz.homelinux.org, used the preciously generated username. On this connection run the mc whitout any problems.
So: it is working, and this is a usefull tool to access the growing tc system on rpi. Bela, thank you for it!
t.janos
[attachment deleted by admin]
Welcome
FAQ
Downloads
Wiki
