Matthew Saltzman wrote: > I tried to run system-config-firewall logged in remotely as a normal > user (not root). I am not prompted for root's password. The interface > pops up and the startup splash screen displays, but when the splash > screen clears, it's replaced with an error popup with the message > > org.fedoraproject.slip.dbus.service.PolKit.NotAuthorizedException.org.fedoraproject.config.firewall.auth: > > and buttons labeled "Redo" and "Quit". "Redo" results in the same > popup. Running on the local machine behaves as expected: root password > prompt, GUI opens, interaction is normal. Logging in remotely as root > works as expected too, but that's not a good security practice. > > Is this a bug? (I assume so...) If so, what package? (This is > system-config-firewall-1.2.27-1.fc14.noarch, FWIW.) I had a similar problem with virt-manager, when launched in a remote ssh session, but I don't remember the details. I failed to understand what the designed behavior would have been, this new-fashion "session" concept (dbus, policykit,...) is too confusing for me. In the good old days you just were a specific user and the only thing you had to manage was xauth and DISPLAY (and ssh does it for you)...

I tried to run system-config-firewall logged in remotely as a normal user (not root). I am not prompted for root's password. The interface pops up and the startup splash screen displays, but when the splash screen clears, it's replaced with an error popup with the message org.fedoraproject.slip.dbus.service.PolKit.NotAuthorizedException.org.fedoraproject.config.firewall.auth: and buttons labeled "Redo" and "Quit". "Redo" results in the same popup. Running on the local machine behaves as expected: root password prompt, GUI opens, interaction is normal. Logging in remotely as root works as expected too, but that's not a good security practice. Is this a bug? (I assume so...) If so, what package? (This is system-config-firewall-1.2.27-1.fc14.noarch, FWIW.)