Bug 710061 - Hard to change firewall configuration over DBus in C
Summary: Hard to change firewall configuration over DBus in C
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: system-config-firewall
Version: 15
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Thomas Woerner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-02 11:44 UTC by Marek Kašík
Modified: 2012-08-06 20:06 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-08-06 20:06:22 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
patch adding functions rule_exist, rule_add and rule_remove (2.74 KB, patch)
2011-06-02 11:44 UTC, Marek Kašík
no flags Details | Diff

Description Marek Kašík 2011-06-02 11:44:06 UTC
Created attachment 502507 [details]
patch adding functions rule_exist, rule_add and rule_remove

Description of problem:
Since system-config-firewall uses pickled Python objects as parameters for its DBus functions, it is not easy to use them in C programming language. There is need for changing firewall configuration in gnome-control-center but this is written in C and hence it doesn't has pickle functions available.

The attached patch implements 3 DBus functions (maybe it should be named another way):

boolean rule_exist (string)
  - check whether given rule exists

boolean rule_add (string)
  - add rule (returns True if it added the rule)

boolean rule_remove (string)
  - remove rule (returns True if it removed the rule)

Version-Release number of selected component (if applicable):
system-config-firewall-1.2.29-3.fc15

Additional info:
this blocks https://bugzilla.redhat.com/show_bug.cgi?id=691834

Comment 1 Thomas Woerner 2011-06-03 13:11:03 UTC
"There is need for changing firewall configuration in gnome-control-center"
What exactly do you want to do?

Comment 2 Marek Kašík 2011-06-03 13:27:37 UTC
Hi,

I need to be able to check whether there exist certain rules in the "/etc/sysconfig/system-config-firewall" and set them if not. For example these: "--port=631:udp", "--port=631:tcp", "--port=5353:udp", "--service=ipp-client", "--service=ipp", "--service=samba-client" and "--service=mdns".
I need it to be able to add new network printers which can he hidden by firewall. (the rule_remove function is not so important, it is there for completeness)

Regards

Marek

Comment 3 Thomas Woerner 2011-06-03 14:24:58 UTC
So you want to open up avahi and also other firewall options. Do you know that this has other implications also? How do you make sure that the user knows what you are doing?

"the rule_remove function is not so important, it is there for completeness"
Do you want to open up the firewall and never make it secure again?

For future Fedora versions, firewalld will be the primary firewall solution. It provides an interface to query firewall options and also to enable them for a specified amount of time. If you want to have a look at firewalld, the proof of concept implementation is included in Fedora 15 as a preview.

Comment 4 Marek Kašík 2011-06-03 15:05:57 UTC
Hi Thomas,

thank you for your informations. I'll look at the firewalld.

Regards

Marek

Comment 5 Fedora End Of Life 2012-08-06 20:06:22 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 15. 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 '15' 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 15 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

Comment 6 Fedora End Of Life 2012-08-06 20:06:22 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 15. 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 '15' 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 15 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.