←back to thread

Multiple security issues in GNU Screen

(www.openwall.com)
414 points st_goliath | 2 comments | 13 May 25 11:28 UTC | HN request time: 0.469s | source
Show context
warpeggio ◴[13 May 25 12:09 UTC] No.43971997[source]▶
So ... my tmux lifestyle is objectively superior in this one respect. Excellent.
replies(1): >>43972571 #
exploderate ◴[13 May 25 13:12 UTC] No.43972571[source]▶
Yes, that's why all the cool kids switched to tmux 17 years ago. The only argument the screen camp had was "no serial port support in tmux". To which we answered something about a smaller more modern code base...
replies(4): >>43974033 #>>43974084 #>>43974139 #>>43980419 #
remram ◴[13 May 25 15:38 UTC] No.43974139[source]▶
I switched to tmux and I switched back due to the weird server/session/window/pane model that makes no sense and prevents me from showing different windows or layouts on different clients. 4 levels of objects is ridiculous and when you end up with less capabilities than screen, what are we doing?

I would love to switch to a modern, maintained terminal multiplexer, but it would need to, well, be good at multiplexing.

replies(1): >>43987997 #
1. gitaarik ◴[14 May 25 18:53 UTC] No.43987997[source]▶
Server? I never encouter that while using tmux.

You can just use one session if you like, and if you do, it's the default, so you don't have to do anything special.

Tabs and Windows work similar as in screen as far as I can see.

replies(1): >>43991249 #
2. remram ◴[15 May 25 02:26 UTC] No.43991249[source]▶
No, you can't. Using one session, every client have to show exactly the same panels with the same layout in the same terminal size.