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
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.
I believe that this should cover most needs. Is this proposal acceptable?
If there is no objection and no one is working on this issue now, I
want to do it this week.
I'll do it in a separate branch without touching any existing code in
master branch so nothing will be broken.
If after testing it works, we prepare a new release for lxsession.
This may not be the best solution, but at least I should try to fix it.
Comments and suggestions are welcomed.
------------------------------------------------------------------------------
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
