* PCMan <pcman...@gmail.com> [2010-09-12 10:53]: > Hello list, > After lengthy discussions, to solve the issue that lxsession lacks > locking mechanism making "suspend" and "hibernate" insecure, I'll like > to make a conclusion here. > Here is the proposal and I'm going to do this in a separate branch for > testing. > > 1. Add two config keys to desktop.conf in [Session] group: > * LockScreen=true/false (default to true to be more secure, but > provide a GUI option somewhere to turn it off) > * LockCommand= (default to empty string) > 2. If LockScreen=false, don't do any locking at all. > If LockCommand is set, use that command for screen locking. > Otherwise, fallback to default locking mechanism
What if LockCommand fails? > 3. Perform following default locking mechanism proposed in issue > #3030907 if a specific LockCommand is not set. > > http://sourceforge.net/tracker/?func=detail&aid=3030907&group_id=180858&atid=894871 > Look for usable locking command in this list: > "gnome-screensaver-command --lock", "xscreensaver-command -lock", > "xlock -mode blank". (This list can be expanded later) > 4. If possible, do #3 in a shell script rather than hard coding it in > C source code for easier custimization. See attached shell script (assumes that the running screensave is in PATH), although I am not aware of any other locking commands which could be run from an LXDE session. -- Guido Berhoerster
lxsession-lock.sh
Description: application/shellscript
------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________ Lxde-list mailing list Lxde-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxde-list
