News for hackers. Stuff that matters.
Re:Multiple Security Issues in GNU Screen by PhilipRoman on Tuesday May 13, 2025 @09:56AM (#43973045)
I'm not sure what made "screen" integrate the two separate pieces of functionality - you can use something minimal like "tio" for serial port access and it's much more elegant.
Re:Multiple Security Issues in GNU Screen by JdeBP on Tuesday May 13, 2025 @11:00AM (#43973708)
It's not separate functionality. The back end (so-called "master" side) of a pseudo-terminal is almost (bar initialization of line speed, hardware flow control, and framing settings) indistinguishable from a "null-modem" call-out serial port or parallel port terminal device. Write a software terminal emulation program for the former, which of course is what screen has, and you already have one for the latter.
Re:Multiple Security Issues in GNU Screen by kevin_thibedeau on Tuesday May 13, 2025 @10:31AM (#43973413)
It isn't separate functionality. Terminals connected via serial port is a valid use case for a terminal multiplexor.
Re:Multiple Security Issues in GNU Screen by PhilipRoman on Tuesday May 13, 2025 @11:01AM (#43973724)
In theory you're correct, but by that logic you'd also have to add ssh (probably by far the most common way of connecting to a remote terminal today). I guess you'd end up with something like mobaXTerm which is a valid approach for sure, but doesn't compose as well.

Personally I live by the maxim "if it can be separated without significant drawbacks, then it should be separate" but GNU tends to see it differently.

Re:Multiple Security Issues in GNU Screen by throwaway173738 on Wednesday May 14, 2025 @04:49PM (#43989062)
I dont think you understand what a terminal is. What you’re talking about is a shell running in a console. What we’re talking about is the terminal to connect to the console serial port running the shell.

EG https://en.m.wikipedia.org/wiki/VT220