Re:Multiple Security Issues in GNU Screen
by kevin_thibedeau on Tuesday May 13, 2025 @09:44AM
(#43972924)
Tmux doesn't support serial ports.
[ Parent
| on HN ]
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.
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.
I'm sure a rewrite of screen in Rust will be 105% secure. And won't support serial ports either.
What is a serial port and what do you use it for?
It is a port that has two data lines, RX and TX, and data is sent in a serial fashion across those data lines. It is used today for embedded systems, routers and switches et al, and getting a console on any machine that doesn't have a gpu with a monitor attached.
USB is a serial BUS, which allows multiple devices; serial ports are single device (if my memory serves).
When most people use the term "serial port" they're referring to a DB-25 or DE-9 port you find on older computers or USB dongles. It's also seen in 8P8C (aka "RJ45") form sometimes, especially in industrial equipment. It can send and receive "characters" (anywhere from 5-8 bits each) one at a time at a fixed rate, either half duplex or full duplex. They usually implement one or more of the RS232, RS422, or RS485 standards.
Originally, you communicated with the computer using a teletype or video terminal connected to a serial port. Whatever you typed went to the computer, and whatever the computer sent back was printed on your terminal screen (or paper in the case of a teletype).
The UNIX (and thus, Linux) command line environment still works this way, except the serial line is virtual.
console=ttyS0,115200