[opensuse-factory] Lock tty session automatically when lock screen in GUI?

I am just wondering, because I do zypper dup in tty rather than an x-terminal, but that also means whenever I am leaving my laptop unattended, the tty session can be easily accessed by someone knowledgeable about the process, because the x screen lock does not lock out access to the tty screen as well. Someone could easily cancel my command, and have access to my user-level privileges. Does anyone know of a way to lock out the tty session automatically after the x screenlocker is invoked?

27.06.2016 19:57, Chan Ju Ping пишет:
I am just wondering, because I do zypper dup in tty rather than an x-terminal, but that also means whenever I am leaving my laptop unattended, the tty session can be easily accessed by someone knowledgeable about the process, because the x screen lock does not lock out access to the tty screen as well.
Someone could easily cancel my command, and have access to my user-level privileges.
Does anyone know of a way to lock out the tty session automatically after the x screenlocker is invoked?
You can run zypper in screen (actually you /should/ run zypper in screen) and lock screen then.

On Monday, June 27, 2016 8:05:46 PM CDT Andrei Borzenkov wrote:
27.06.2016 19:57, Chan Ju Ping пишет:
I am just wondering, because I do zypper dup in tty rather than an x-terminal, but that also means whenever I am leaving my laptop unattended, the tty session can be easily accessed by someone knowledgeable about the process, because the x screen lock does not lock out access to the tty screen as well.
Someone could easily cancel my command, and have access to my user-level privileges.
Does anyone know of a way to lock out the tty session automatically after the x screenlocker is invoked?
You can run zypper in screen (actually you /should/ run zypper in screen) and lock screen then.
Understood. Thanks for the suggestion!

On 2016-06-27 19:05, Andrei Borzenkov wrote:
You can run zypper in screen (actually you /should/ run zypper in screen) and lock screen then.
Screen has a facility for locking it? I use tmux, I haven't noticed such a feature. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)

On Mon, Jun 27, 2016 at 08:54:16PM +0200, Carlos E. R. wrote:
On 2016-06-27 19:05, Andrei Borzenkov wrote:
You can run zypper in screen (actually you /should/ run zypper in screen) and lock screen then.
Screen has a facility for locking it? I use tmux, I haven't noticed such a feature.
man tmux http://askubuntu.com/questions/22125/lock-tmux-session-with-vlock Best regards, S_W

Andrei Borzenkov <arvidjaar@gmail.com> writes:
27.06.2016 19:57, Chan Ju Ping пишет:
I am just wondering, because I do zypper dup in tty rather than an x-terminal, but that also means whenever I am leaving my laptop unattended, the tty session can be easily accessed by someone knowledgeable about the process, because the x screen lock does not lock out access to the tty screen as well.
Someone could easily cancel my command, and have access to my user-level privileges.
Does anyone know of a way to lock out the tty session automatically after the x screenlocker is invoked?
You can run zypper in screen (actually you /should/ run zypper in screen) and lock screen then.
And if you use screen (or tmux) you don't need a separate tty session. Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 2016-06-28 09:29, Andreas Schwab wrote:
Andrei Borzenkov <arvidjaar@gmail.com> writes:
And if you use screen (or tmux) you don't need a separate tty session.
I typically start a tty session, start a new tumx session, then go back to X, and there attach to the same session. You say this is not needed? If I create the tmux session on the desktop only and this one dies, tmux survives? -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)

"Carlos E. R." <robin.listas@telefonica.net> writes:
You say this is not needed? If I create the tmux session on the desktop only and this one dies, tmux survives?
That's the point of it, but I only know about screen. Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (5)
-
Andreas Schwab
-
Andrei Borzenkov
-
Carlos E. R.
-
Chan Ju Ping
-
Tomáš Čech