Restore SSH session after network breakdown (not using SCREEN)

This question bothers me for so long - is there any way to restore ssh (pts) session after client's disconnetion?

Here is an algorythm:
1. # ssh
2. open several interactive programms (mc, vim etc)
3. plug of network cable from client's computer :-)
4. open ssh connection from another computer and run:
    # who
    username   pts/3        Apr 10 14:04 (   <------ this session must be restored
    root    pts/6        Apr  2 11:04 (
    root    pts/7        Apr  5 15:39 (
5. huh? what to do?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

No, because the cryptographic state has been broken.

If what you suggest were possible, then that would open SSH up to session hijacking, where an attacker impersonated the client of another session.

Security is balancing functionality/convenience with good defenses. You're looking for a convenience from a tool designed to provide good defenses.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
OLEshiy, hi.
I'm completely agree with PsiCop, you cannot connect to already dead session.
However _theoretical_ small possibility exists, on modified system.
OpenSSH uses openpty() library call (libutil) to allocate a pseudo terminal device. This call is implemented differently on different systems, but on Linux it opens '/dev/ptmx' and /dev/pts/* devices (by name) to find first free pseudo terminal. So, it's theoretically possible to fake /dev/ptmx and create a node with the same name, but your own pseudo terminal multiplexor driver with some  controlling process in a user space (much like screen). Then you may write program that can 'reconnect' such disconnected process and view the last screen. However you cannot fake 'ssh' to think that this tcp session is still alive (as correctly said by PsiCop) and any input will disconenect stale ssh session and kill your sshd.
Please enlighten me.

 I believe to have heard before that someone say that this is possible. On the server side you would have to make the TTL of the session to last longer and that the client has a fix ip. In order for SSH to work, you would require a 3 factor authentication which is the IP address, Application ID and also the SSL cert.

One can spoof the ID and maybe the Application ID but not the same cert right? The user will still need to relogin username and password to continue its session. I've seen it working but not the actual steps on how its being done. The reason behind it was that dial-up users which has slow connectivity find it a hassle if the connection drops half way and their password gets locked.
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

> dr_shivan
It seems you have missed some stuff from the original post

You say:
> On the server side you would have to make the TTL of the session to last longer *and that the client has a fix ip*

And what OLEshiy asked for:
> 4. open ssh connection from *another* computer and run:
dr_shivan, really I tested such 'session restoration' what you are talking about, but from the same host (FreeBSD with some minor TCP tuning)
to restore/resume a session, you can use VNC or freenx (NX client).
VNC is packaged in most of Linux distribution.
freeNX and NX client you can download from

Basically, those two tools allow you to resume/restore the remote terminal session, doesn't matter via telnet or SSH.
It allows you to resume/restore from other machine as well.
OLEshiyAuthor Commented:
Ok, let me paraphrase my question: is there any way to connect to existing pseudo-terminal (analogue to screen -x)?
As you've said above, every ssh-connection opens (or creates?) pseudo terminal. When netwotk connection breaks down, that pts remains alive for some time (according to such sshd configuration as "timeout", "keepalive" etc). I have root privelegies on the server.
VNC or NX can fit your need just fine.
You can resume the VNC or NX session from any other machine if the network connection breaks down.
Those tools basically keep the session alive, unless you kill then or reboot, even thouth the network connection breaks down.
ssh or SSL for VNC or NX is used to encrypted the connection from client to server. After connection, it looks for the existing session first.
So you can easy to resume your session without deal with restoring ssh session.

I use NX/VNC at work and suspend it when I leave for home. Then resume the session at home when I need it.
OLEshiyAuthor Commented:
Thanks for all advices, but I still haven't heard an answer to my last question: is there any way to connect to existing pseudo-terminal?
> is there any way to connect to existing pseudo-terminal?

sirbounty, hi.

The correct answer is here, was first suggested by PsiCop. There is _no_ possible way to connect to dead ssh session and it _is_ correct answer.
Forced accept.

EE Admin
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
SSH / Telnet Software

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.