←back to thread

Multiple security issues in GNU Screen

(www.openwall.com)
414 points st_goliath | 7 comments | 13 May 25 11:28 UTC | HN request time: 0s | source | bottom
1. zoobab ◴[13 May 25 12:46 UTC] No.43972333[source]▶
I emailed the author of GNU Screen about the lack of proper documentation about the logging to a file feature:

http://www.zoobab.com/screenrc

GNU need a better issue tracking system :-)

replies(3): >>43972876 #>>43981355 #>>43982965 #
2. CelestialMystic ◴[13 May 25 13:40 UTC] No.43972876[source]▶
There was a Q&A with the author of Tmux. He was complaining about the lack of documentation ~16 years ago.

https://undeadly.org/cgi?action=article&sid=20090712190402

replies(1): >>43973069 #
3. anthk ◴[13 May 25 13:59 UTC] No.43973069[source]▶
Tmux has been in OBSD base side several releases and documented since the first one.
replies(1): >>43973112 #
4. CelestialMystic ◴[13 May 25 14:04 UTC] No.43973112{3}[source]▶
I know. I suggest you read the Q&A I posted.
replies(1): >>43976302 #
5. ◴[13 May 25 18:50 UTC] No.43976302{4}[source]▶
6. amszmidt ◴[14 May 25 06:09 UTC] No.43981355[source]▶
It is documented in detail in the GNU screen manual, https://www.gnu.org/software/screen/manual/screen.html#Log
7. Avamander ◴[14 May 25 10:49 UTC] No.43982965[source]▶
> GNU need a better issue tracking system :-)

This is a problem with quite a few older projects, that issues get buried in the endless depths of unindexed mailing lists, if at all. People bemoan Discord (rightfully) for making info like this unaccessible, but IRC (that some projects still use) is basically twice as bad.

I really wish these projects would migrate to Gitea/Forgejo/Codeberg, GitLab or GitHub or anything like that, just to bring these things together and provide vital discoverability.