Indeed, PolicyKit should be repaired to allow a remote sessions permission to do something. But FreeNX/NX must be fixed to create a valid session.
My solution corrects FreeNX/NX but just workaround PolicyKit problem. But I must say that in some cases this solution has a SECURITY IMPLICATION. Like I've showed in the proof of concept, the solution can act like a "sudo" and sudo my itself is an workaround. The problem is that a remote session should have the permission to gain admin right only if it is explicitly allow to do so. This happens only if you have admin rights but don't have "sudo" permission. Don't apply to Ubuntu, since the admin group has sudo permission by default. But I think Fedora/Red Hat don't uses "sudo" by default. Everybody that uses this fix must be aware of this problem. -- Policy Kit Unlock Buttons Greyed Out when using NX https://bugs.launchpad.net/bugs/221363 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
