Timeline for tmux: Lock session only when using tmux on console, not from a graphical DE
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 9, 2021 at 9:50 | vote | accept | genodeftest | ||
| Jul 8, 2021 at 22:31 | comment | added | Kamil Maciorowski | Good news is lock-command vlock runs vlock where the tmux client runs, so it can lock each client independently and it can test what the tty is. However in my Kubuntu your original setup led me to a situation where a non-graphical terminal returned to the tmux session after I failed to authenticate in vlock. I wonder if there's a bug or I'm missing something. Please confirm that the setup in question really prevents attackers from getting inside tmux in your case. | |
| Jul 8, 2021 at 22:21 | comment | added | Panos | I think that you have to think the logic behind this a bit more. What about attaching tmux both to a ssh session AND a graphical terminal emulator? | |
| Jul 8, 2021 at 22:16 | answer | added | Kamil Maciorowski | timeline score: 4 | |
| Jul 8, 2021 at 21:50 | comment | added | genodeftest | About the logic: How could this look like? Specifying a script instead of the vlock command which (depending on the tmux client) would either exec vlock or terminate? | |
| Jul 8, 2021 at 21:49 | comment | added | genodeftest | Thanks for the question! Is it possible to lock the client instead of the server? Then this logic would be easier… | |
| Jul 8, 2021 at 19:36 | history | asked | genodeftest | CC BY-SA 4.0 |