Timeline for ssh -> screen -> ssh - how to kill remote screened ssh without killing original ssh session
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 12, 2023 at 17:55 | history | edited | Jim | CC BY-SA 4.0 |
fixed typo
|
| Sep 4, 2015 at 12:59 | comment | added | galaxy | This is unrelated to the question, but related to the used insecure approach (of interactively ssh'ing to remote systems from remote systems) -- you may consider to properly tunnel your traffic without exposing your credentials on the intermediate hosts, see: dmitry.khlebnikov.net/2015/08/… | |
| Sep 3, 2015 at 19:42 | comment | added | thrig | (I actually never kill any of the sessions, and just leave them all running.) | |
| Sep 2, 2015 at 21:56 | vote | accept | Jim | ||
| Sep 2, 2015 at 21:51 | history | edited | Jim | CC BY-SA 3.0 |
added 1 character in body
|
| Sep 2, 2015 at 21:49 | answer | added | Tom Hunt | timeline score: 6 | |
| Sep 2, 2015 at 21:48 | comment | added | Jim | Wow! what's up buddy?? No, that's the point. I'm in an already running screen session. Did I understand what you were saying? | |
| Sep 2, 2015 at 21:47 | history | edited | Jim | CC BY-SA 3.0 |
additional context and spelling fix.
|
| Sep 2, 2015 at 21:46 | comment | added | thrig |
Consider instead screen -x to attach to an already running session without booting off your other connection?
|
|
| Sep 2, 2015 at 21:40 | history | asked | Jim | CC BY-SA 3.0 |