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]

Re: Keeping OpenSSH connections alive

Subject: Re: Keeping OpenSSH connections alive
Date: Fri, 17 Jun 2005 12:35:28 -0500
On Friday 17 June 2005 10:28 am, JCA wrote:
   The bottom line is, is there a way to coax A to keep its OpenSSH
forked processes alive for a prespecified time, no matter what their
matching ssh clients in B are doing? Why is it the case that the three
lines I added to the sshd_config file do not pull it off? Something to
do with the TCP stack overriding them perhaps?


Would just running screen on the server after you log in do the trick for you? 
That's what I do when using my laptop as a client. Works great!

If you lose your connection for any reason, just log back in, issue screen -r, 
and pick up where you left off. 

-Gregg

<Prev in Thread] Current Thread [Next in Thread>