https://bugzilla.novell.com/show_bug.cgi?id=637215 https://bugzilla.novell.com/show_bug.cgi?id=637215#c16 --- Comment #16 from Don Hughes <support@microtechniques.com> 2010-09-08 12:07:29 UTC --- If you take the comments in permissions.paranoid literally, they do not make any sense at all. 1) It says that it can not be used in a single-user or a multi-user installation, and I believe that that just about covers everything except virtual, negative, and imaginary users. 2) It says that it might be useable for non-privileged users EXCEPT for simple tasks - implying that it is useable for complex tasks(?). Vincient, You say "that running X as root and having paranoid PERMISSION_SECURITY is weird: you should never run a desktop session as root". However, with paranoid PERMISSION_SECURITY, the only way that you CAN run X is as root. I have an application server that, unfortunately, requires a gui for some of its configuration. Normally, no one is logged into the system. I chose permissions.paranoid for the reduced attack exposure. When I need to make configuration changes, I start X. If you have suggestions for an alternative setup, I would appreciate your input. If permissions.paranoid was not intended to be used without modification, please rename it to permissions.paranoid.template, or permissions.paranoid.example; and please edit the comments. Regardless of how the permissions got changed - either through PERMISSION_SECURITY or manually - gnomesu should fail a little less obtusely. I have had this problem for a number of months, and it was not obvious that it was really a permissions issue. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.