Topic: [Solution] DE session hosted tty in suspended error
I was just researching slock, when I read claims about its failure against tty. Not that the scenario is any different from users switching terminal screens for some reason. I recall that tty might be for OS installation and setup, but the internet may find new things about tty. After reading some instructions, I test tty (Ctrl + Alt + F# keyboard buttons) during DE session on a different OS. Nothing much, save for the login prompt. I returned to the currently active tty, which logs me back to the DE session.
Now, it is the moment of truth, I test tty on my Hyperbola GNU/Linux-libre OS setup. When I went back to the DE session, the hosting tty takes me back to console session with an error. The error just hangs there. I tried tap keystrokes on Ctrl + C keyboard buttons. They cancel the error as suspected, but I am now on console session. Tapping Ctrl + C keyboard buttons again log me out to console login prompt. Dreading about the cancel command with such powers despite specific conditions, I decided to test tty against slock.
I activated slock, then rerun the tty test. To my dismay, the error manage to override both slock lockscreen function and DE session. With one cancel command, I was able to run and write files/functions without effort. I even log back into DE session. tty on this OS is a major vulnerability that needs to be taken care of asap.
Research provided hints about slock's security consideration. After learning the fix, whereabouts of the xorg config file in question, remains to be seen. I later found a list of possible directories hiding the xorg confile file. Finally, I found a directory path with config files, but which ones? Since the error conflicts with DE, I assume video drivers. Fix of video driver config files and a reboot, managed to prevent access to tty screens. Hyperbola GNU/Linux-libre is a step closer to service/function freedom.
Upon reflection, the incident made me think about possible causes. Since patching up the video drivers, I blame video drivers as the fault actors. No doubt that they support DE, but there is culpability for misconfiguration. Imagine if an evil maid attack (or cyberattack) breach a OS this way? Easy pickings, easy pickings. Cover-ups too!
Proprietary brands that create backdoors, expose victims to trespassing. In the light of this situation, civil action, (libre) MFA, and libre VGA/SDL drivers must stand for liberty and justice for all.
https://man.archlinux.org/man/xorg.conf.5.en
https://man.archlinux.org/man/slock.1.en
# nano /usr/share/X11/xorg.conf.d/##-videodriver.conf
Within /usr/share/X11/xorg.conf.d/##-videodriver.conf, check that the following parameter values are set in place.
Section "OutputClass"
Identifier "?"
MatchDriver "?"
Driver "?"
EndSection
Section "ServerFlags"
Option "DontVTSwitch" "True"
Option "DontZap" "True"
EndSection
# reboot
Test tty during DE session.
---
I encourage people to write these instructions to the video driver installation page. The more and faster good people know about it, the better. I know that this topic may put a dent on Hyperbola GNU/Linux-libre, but as long the pace is on cue, things will improve in effort and time. I'm am sure that this is not the first blunder in GNU/Linux-libre development so things should be looking up.
https://wiki.hyperbola.info/doku.php?id … stallation
I also suggest implementation of (libre) PAM, even if it was by custom installation. Vetting packages to libre standards would help accomplish goals. A far fetch idea is a libre VGA/SDL. These functions have consistently work when graphic cards may fail to render (or even allow unauthorized user privileges) for a variety of reasons.