Bug 649566 - system-config-firewall doesn't authenticate
Summary: system-config-firewall doesn't authenticate
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: system-config-firewall
Version: 14
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Thomas Woerner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-04 01:06 UTC by Jim Haynes
Modified: 2012-08-16 21:16 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-16 21:16:39 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jim Haynes 2010-11-04 01:06:30 UTC
Description of problem:If I as an ordinary user do system->administration->firewall  it doesn't ask me for authentication and
just goes away after I click away the first screen


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:
Should ask for authentication and then let me configure the firewall

Additional info:
I have SELinux disabled

Comment 1 Thomas Woerner 2010-11-08 13:05:16 UTC
Is there a SELinux error message also?

Comment 2 Jim Haynes 2010-11-08 16:00:15 UTC
This is related to bug 649553

At the time I had selinux disabled.  I have blown away that installation so
if there were other error messages logged I no longer have them.

Now I have selinux enabled, and when I try to run system->administration->
firewall I get an error
org.fedoraproject.slip.dbus.service.PolKit.NotAuthroizedException.org.fedoraproject.config.firewall.auth:

However when I run it from a different user account I made for testing it
works as it should, asks for the super user password.

So as with bug 649553 there is something in my own user environment that
is causing the misbehavior.  I have no idea what it is.

Comment 3 Matthew Saltzman 2011-01-02 20:13:04 UTC
I see this when I run system-config-firewall when logged in from a remote machine with as a normal user using "ssh -X".  On the local machine, or when logged in remotely as root, I don't see this behavior.  When logged in as a normal user on the local machine, the GUI opens with a splash screen, and when the splash screen is dismissed, the root prompt popup appears.  When logged in remotely, the GUI opens with the splash screen.  When the splash screen is dismissed, the error pops up.

Comment 4 Jim Haynes 2011-01-02 21:10:38 UTC
OK.  In my case, when I'm logged in as myself locally on the X window
system, when I do System->Administration->Firewall I first get the Firewall
Configuration startup box on top of the firewall configuration window.
When I dismiss that I get 
org.fedoraproject.slip.dbus.service.PolKit.NotAuthorizedException.org.fedoraproject.config.firewall.auth:

but if I am logged in as a different user than my usual login name it seems
to work as it should.  So there seems to be some obscure thing in my personal
environment that upsets the authentication in this and in some other
applications.

Comment 5 Fedora End Of Life 2012-08-16 21:16:42 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


Note You need to log in before you can comment on or make changes to this bug.