openssh bugs - Apr 2007 - [Bug 1304] SSH session cleanup problem

http://bugzilla.mindrot.org/show_bug.cgi?id=1304

           Summary: SSH session cleanup problem
           Product: Portable OpenSSH
           Version: 4.6p1
          Platform: ix86
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: ssh
        AssignedTo: bitbucket at mindrot.org
        ReportedBy: sumit_1636 at yahoo.com


Hi,
I am facing this problem with sshing into another system.
What I am doing is:
ssh root at 192.168.61.136

Now, this prompts me for password and let me login to 192.168.61.136
where sshd is running.
Now, I open up another temrinal window of my local machine and do:
ps -eaf  | grep ssh

This shows the ssh session opened with 192.168.61.136 machine.
Now, I open a terminal window of 192.168.61.136 machine and reboots the
system. NOTE: on this machine sshd is running.

Now, ideally since 192.168.61.136 is gone down, the process table
should have the entry for ssh session deleted.
BUt on doing ps -eaf | grep ssh on my local machine, I still see the
ssh session process running.

I dont know if its a bug or not. Kindly update me on this.

Thanks,
Sumit




------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugzilla.mindrot.org/show_bug.cgi?id=1304


sumit_1636 at yahoo.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |sumit_1636 at yahoo.com






------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugzilla.mindrot.org/show_bug.cgi?id=1304





------- Comment #1 from dtucker at zip.com.au  2007-04-10 09:23 -------
You reboot the server, ie the one that sshd is running on, and the sshd
process survives?  Short of some kind of external checkpointing
software, I don't see how that's possible.

In its normal configuration, sshd will start as a listening process, ie
there will always be at least one sshd even if nobody has logged on via
ssh.  This is normal.

On a system that supports setproctitle (which Linux does) you will see
something like this in the process table:

# ps -eaf | grep sshd
root     25072     1  0 Apr06 ?        00:00:01 /usr/sbin/sshd
root     26965 25072  0 Apr09 ?        00:00:00 sshd: dtucker [priv]
dtucker  26967 26965  0 Apr09 ?        00:00:07 sshd: dtucker at pts/0

In this example there is one login via sshd.  Process 25072 is the
listening daemon, 26965 is the privileged process that looks after my
login and 26967 is the one that does most of the work for me.

In its normal configuration, sshd is not like, eg, telnetd which is
started from inetd.  It's possible to configure sshd to run from inetd
but it's not normally done that way (mainly because it's slower).




------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.