Bug 1097765

Summary:	at_console in dbus policy makes firewalld hard to use on servers
Product:	Red Hat Enterprise Linux 7	Reporter:	Thomas Woerner <twoerner>
Component:	firewalld	Assignee:	Thomas Woerner <twoerner>
Status:	CLOSED ERRATA	QA Contact:	Tomas Dolezal <todoleza>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.1	CC:	jpopelka, jscotka, stefw, twoerner
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1094745	Environment:
Last Closed:	2015-03-05 13:23:07 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1094745
Bug Blocks:	1094121

Description Thomas Woerner 2014-05-14 13:31:05 UTC

+++ This bug was initially created as a clone of Bug #1094745 +++

Description of problem:

Use of at_console="true" in the firewalld DBus policy file makes firewalld hard to use on servers, where users are logged in via ssh, or via Cockpit, but not at a console.

at_console="true" is a real old relic, that was never really implemented. Modern services should be using polkit.

NetworkManager moved away from it for the same reasons (want to be usable on servers): bug #979416

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

firewalld-0.3.9.3-1.fc20.noarch

[stef@stef firewalld]$ git grep at_console
config/FirewallD.conf:  <policy at_console="true">

--- Additional comment from Thomas Woerner on 2014-05-14 09:29:54 EDT ---

Fixeds upstream in 
https://git.fedorahosted.org/cgit/firewalld.git/commit/?id=449e5b97b40e3363495391bfa4ba6c4c1aebb926

Comment 2 Thomas Woerner 2014-05-28 11:57:56 UTC

Fixed upstream: https://git.fedorahosted.org/cgit/firewalld.git/commit/?id=449e5b97b40e3363495391bfa4ba6c4c1aebb926

Comment 7 errata-xmlrpc 2015-03-05 13:23:07 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-0520.html