Bug 32661

Summary:	Stopping sshd doesn't kick currently connected users.
Product:	Gentoo Security	Reporter:	Ahmed Farid <afw2000>
Component:	Vulnerabilities	Assignee:	Gentoo Security <security>
Status:	RESOLVED INVALID
Severity:	major
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

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