firewall apparently disabled until you authenticate

Bug #850468 reported by Martin Pool
This bug affects 7 people
Affects Status Importance Assigned to Milestone
Fix Released

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

Revision history for this message
costales (costales) wrote :

Hi! :)
The default ufw status in a fresh installation is disabled, Gufw uses a 'generic' status for this button for don't give a 'real' information.
I think this is a right status. Is there any usability rule about this? Have you an idea for improvement it? :)
Best regards and thanks for the bug.

Revision history for this message
Martin Pool (mbp) wrote : Re: [Bug 850468] Re: firewall apparently disabled until you authenticate

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

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?)

Revision history for this message
costales (costales) wrote :

Hi! I really like the second:
   "Replace it with text saying unlock to show status"
jbicha did this change with the unlock button, but we had a wrong behavior with the events.
I'll try do it for Ubuntu 12.04 :)
In other way, the incoming & outgoing dropbox has the same issue.
Best regards Martin :)

Revision history for this message
Patrick Chan (patrickmcc) wrote :

 developer from dev core team, patrick.
im currently lestening from launchpad and heard things about ur issues, im heading u a list for rescuing ur details,
here's the solution,

1. launch the terminal for devmode use,
2. replace the key with unlock status for dev-ops.
3. hid the radiobutton for captitable options until its unlocked
3. replace it with its saying unlock to see the staus (usually requires people to auth the app for the highest administration with password) and auth the gufw for root at all.

finally u'll resolve the problem uve met

best regards Patrick ;)

costales (costales)
Changed in gui-ufw:
status: New → Confirmed
Revision history for this message
Musa Ibraheem (musa-ibraheem) wrote :

Patrick McCosker, could we please have a description of the bugfix in English, please? I'm pretty handy with the Terminal, but I'm not quite at the level of Ubuntu Demigod yet. Also, am I right in inferring from this thread that the "Off" status on Gufw merely means that the interface is inactive, but upon unlocking Gufw, it will confirm the Terminal's output that Ufw IS in fact active, and the rules set are still in effect?

Revision history for this message
costales (costales) wrote :

Implemented for 13.10. Thanks! ;)

Changed in gui-ufw:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers