So, without citing chapter and verse, I think it's a pretty good ui rule that if the app "doesn't know" whether the firewall is enabled or not, it shouldn't pretend to know about it. The fact that it's disabled in a clean installation is not really persuasive to me - on a machine with gufw installed, perhaps it's pretty likely that it is installed?
Some options: * hide the radiobutton until it's unlocked * replace it with text saying "unlock to show status" * require people to authenticate to use gufw at all (since it seems that you can't do anything as non-root?) -- You received this bug notification because you are a member of Gufw Developers, which is subscribed to Gufw. https://bugs.launchpad.net/bugs/850468 Title: firewall apparently disabled until you authenticate Status in Gufw: New Bug description: In Oneiric: 1- install gufw etc, and start it 2- click the lock and authenticate 3- turn the firewall on 4- quit 5- (optionally, verify from the terminal that the firewall is still active) 6- restart ufw what happens: it shows "Firewall status: off" (greyed out), until you authenticate what should happen: if the firewall state can't be reported until you authenticate, gufw shouldn't show something that looks like it's actually off To manage notifications about this bug go to: https://bugs.launchpad.net/gui-ufw/+bug/850468/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~gufw-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~gufw-developers More help : https://help.launchpad.net/ListHelp
