Red Hat Bugzilla – Bug 170488
"screen" support would be good
Last modified: 2007-11-30 17:11:15 EST
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050923 Epiphany/1.6.5 Description of problem: vlock -a does not lock all screens, i.e. ^a^n will move to the password unprotected screen. It would be nice if vlock warned users that it was running from within screen (screen has it's own locking function). Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: x Additional info:
*** This tty is not a VC (virtual console). *** *** It may not be securely locked. *** This TTY is now locked. Please enter the password to unlock. root's Password: Do you think that the sentence "It may not be securely locked." is not enough? Well, I can add there some next extra message like "You're probably runnig screen(1). Please, check screen documentation for correct locking.". But I think the the actual warning is almost enough.
The message "it may not be securely locked" shows when you try to lock a virtual console, but the docs say this message appears because virtual console locking has been given less testing than real console locking. When I run vlock from inside screen, the console is *definitely* not securely locked - I can run ^AC to create a new console. A screen specific warning would be good I think.
Done. Update to vlock-1.3-22.
Note that fixed in the development branch (FC5).
Thanks!