Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 32661 - Stopping sshd doesn't kick currently connected users.
Summary: Stopping sshd doesn't kick currently connected users.
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Security
Classification: Unclassified
Component: Vulnerabilities (show other bugs)
Hardware: All Linux
: Normal major (vote)
Assignee: Gentoo Security
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-11-03 16:11 UTC by Ahmed Farid
Modified: 2011-10-30 22:41 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ahmed Farid 2003-11-03 16:11:18 UTC
as i said in the summary, i know this isn't big but still..
atleast add like an "stopkill" to the init.d script to stop and kill all currently logged in users.
a simple "killall sshd" will do.

peace
Comment 1 SpanKY gentoo-dev 2003-11-03 16:20:36 UTC
i dont agree with this ...

i see `/etc/init.d/sshd stop` as killing the listening daemon, which it does
... not as a 'lets kill all the sshd sessions' ...
a `killall sshd` would bug if the user is running sshd's on custom ports
... only way would be to do a parent/child check of the original sshd daemon
...
Comment 2 Kurt Lieber (RETIRED) gentoo-dev 2003-11-03 16:46:10 UTC
just to chime in, it would be a Very Bad Thing if /etc/init.d/ssh stop killed
listening ssh daemons.  People would then have no easy way to restart sshd
remotely -- a b0rked config would have drastic consequences.

Comment 3 Martin Holzer (RETIRED) gentoo-dev 2003-11-03 16:54:45 UTC
no distro used this dirty method