Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Secure-Shell
[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

RE: X11 Forwarding

from [Jeff Rosowski] Network Security [Permanent Link]
Subject: RE: X11 Forwarding
Date: Tue, 19 Apr 2005 16:32:31 -0700 (PDT) 
I have learned the hard way that sshd cannot be restarted remotely (sshd
does not respond to HUP).  Apparently, sshd forks a new sshd process
when a new connection is made and the new sshd process reads the config
file anew.  Therefore, there shouldn't be any need to restart.

If you kill off only the original sshd it won't kill off the active sshd connections. Then you can restart it. I'm paranoid and run two instances of ssh, so I have a backdoor in case one process gets killed off and I drop my connection.

[More with this subject...]




<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  Re: publickey/password login, Jeff Rosowski
Next by Date:  RE: X11 Forwarding, Foster, Dale
Previous by Thread:  Re: X11 Forwarding, Greg Wooledge
Next by Thread:  RE: X11 Forwarding, McDougall, Marshall (FSH)
Indexes:  [Date] [Thread] [Top] [All Lists]