"Lock" function needs to not be gnome-screensaver
Bug #430979 reported by
Jordan Erickson
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Thin Client Manager NG |
Triaged
|
Medium
|
René Fleschenberg | ||
Bug Description
The "Lock" function needs to be something other than Gnome-screensaver, as this app simply starts the screensaver for the user, allowing them to enter their own password in to unlock it. Yanqui had mentioned a good app that simply blanks the screen and locks user input. I don't recall what this was, but it seemed like it would be a good candidate. All in all, the "Lock" function needs to lock the terminal and *only* allow an administrator to unlock it (whether from TCM or from the terminal in a hidden password input, or something), since an administrator locked it in the first place.
| Changed in tcm-ng: | |
| assignee: | nobody → René Fleschenberg (rene.f) |
| importance: | Undecided → Medium |
| status: | New → Triaged |
Revision history for this message
| René Fleschenberg (rene.f) wrote | #1 |
To post a comment you must log in.
We could probably use xlock, if it supported the -cpasswd option as described in the manpage. Unfortunately, the xlock in Ubuntu does not support that option. Right now, I don't know what else there is that we could use.
We might end up having to write our own utility, or ship a custom built version of xlock. Both of these possibilities are not nice.
This issue needs more thought. Josh, do you have any ideas on this one?