sshd doesn't stop after stopping

[GoogleCodeExporter]

What steps will reproduce the problem?
1. start droidsshd v0.6 in android/root mode
2. connect with ssh-client
3. stop droidsshd on the phone
4. check on the client if you are still connected and can issue commands
5. kill droidsshd with a 'task manager'
6. try again on the client if you are still connected

What is the expected output? What do you see instead?
I would expect that after stopping the daemon manually that, guess it, the 
daemon is down. Instead it seems that it is still running and you can issue 
commands from your ssh-client.

What version of the product are you using? On what operating system?
droidsshd v0.6 on Android 2.1.1 on a Motorola Milestone/Droid. Instead of the 
standard Android shell (sh) I use bash (compiled from someone third, 
xda-developer).

Original issue reported on code.google.com by s3.hu...@gmail.com on 20 Jan 2011 at 6:37

[GoogleCodeExporter]

The dropbear daemon actually stops accepting new connections when 'stopped', 
but any ongoing/open sessions are allowed to keep running/opened until 
finished/closed properly. AFAIK, this is the 'standard' behavior for both 
dropbear and openssh - this way, one is allowed to do things like change 
configuration and restart daemons without being kicked out immediately at 
daemon stop/restart (and possibly getting locked out of the machine if for some 
reason the daemon refuses to start due to some config error, etc...).

Original comment by augu...@bott.com.br on 22 Jan 2011 at 7:59

• Changed state: Invalid

[GoogleCodeExporter]

Ok, I don't have much know-how about ssh yet. I'll consider it as feature
not a bug from now on. Thanks for answering!

Original comment by s3.hu...@gmail.com on 23 Jan 2011 at 10:10