Ahem... I'm just putting out feelers for ideas (a.k.a. best practices if such exist), for how to implement Priviledged Execution for Entrance_Edit_GUI
The problem is that, the config file is /etc/entrance_config.cfg, which is protected file, but all users *can* run entrance_edit_gui for now. Ofcourse, I could just install /etc/entrance_config.cfg writable by everyone (brilliant huh? I love me!), but that's not so practical. On the commandline, I can use 'sudo /path/to/entrance_edit_gui', and for some people, it would ask for a password, for others, it won't depeding on my sudo configuration. I think in GNOME, there's a keyring manager of some sort, so with KDE? (i'm trying to find that out) Whats the best practice for implementing stuff like this in a GUI environment? Ideally, if I ran entrance_edit_gui once, and entered my password, it shouldn't ask me again for subsequent runs untill I log out. If I were launching it before Login (from the Entrance login screen itself, it should still work, so this can't be tied to any window manager *ideally*, or it should be able to work with or without one). thoughts and ideas appreciated. Cheers, Essien ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
