-
 KDE-Apps.org Applications for the KDE-Desktop 
 GTK-Apps.org Applications using the GTK Toolkit 
 GnomeFiles.org Applications for GNOME 
 MeeGo-Central.org Applications for MeeGo 
 CLI-Apps.org Command Line Applications 
 Qt-Apps.org Free Qt Applications 
 Qt-Prop.org Proprietary Qt Applications 
 Maemo-Apps.org Applications for the Maemo Plattform 
 Java-Apps.org Free Java Applications 
 eyeOS-Apps.org Free eyeOS Applications 
 Wine-Apps.org Wine Applications 
 Server-Apps.org Server Applications 
 apps.ownCloud.com ownCloud Applications 
--
-
 KDE-Look.org Artwork for the KDE-Desktop 
 GNOME-Look.org Artwork for the GNOME-Desktop 
 Xfce-Look.org Artwork for the Xfce-Desktop 
 Box-Look.org Artwork for your Windowmanager 
 E17-Stuff.org Artwork for Enlightenment 
 Beryl-Themes.org Artwork for the Beryl Windowmanager 
 Compiz-Themes.org Artwork for the Compiz Windowmanager 
 EDE-Look.org Themes for your EDE Desktop 
--
-
 Debian-Art.org Stuff for Debian 
 Gentoo-Art.org Artwork for Gentoo Linux 
 SUSE-Art.org Artwork for openSUSE 
 Ubuntu-Art.org Artwork for Ubuntu 
 Kubuntu-Art.org Artwork for Kubuntu 
 LinuxMint-Art.org Artwork for Linux Mint 
 Arch-Stuff.org Art And Stuff for Arch Linux 
 Frugalware-Art.org Themes for Frugalware 
 Fedora-Art.org Artwork for Fedora Linux 
 Mandriva-Art.org Artwork for Mandriva Linux 
--
-
 KDE-Files.org Files for KDE Applications 
 OpenTemplate.org Documents for OpenOffice.org
 GIMPStuff.org Files for GIMP
 InkscapeStuff.org Files for Inkscape
 ScribusStuff.org Files for Scribus
 BlenderStuff.org Textures and Objects for Blender
 VLC-Addons.org Themes and Extensions for VLC
--
-
 KDE-Help.org Support for your KDE Desktop 
 GNOME-Help.org Support for your GNOME Desktop 
 Xfce-Help.org Support for your Xfce Desktop 
--
openDesktop.orgopenDesktop.org:   Applications   Artwork   Linux Distributions   Documents    LinuxDaily.com    Linux42.org    OpenSkillz.com   
 
Apps
News
Groups
Knowledge
Events
Forum
People
Jobs
Register
Login


Sponsoring


-
- Content .- Fans  .- Knowledge Base  . 

KMyFirewall

   1.1.1  

KDE Security

Score 80%
KMyFirewall
zoom


KMyFirewall
zoom


KMyFirewall
zoom


Link:  Link
Minimum required   KDE 3.3.x
Downloads:  17734
Submitted:  Jan 12 2004
Updated:  Jan 31 2008

Description:

KMyFirewall attempts to make it easier to setup IPTables based firewalls on Linux systems.
It will be the right tool if you like to have a so called "Personal Firewall" running on your Linux box, but don't have the time and/or the interest to spend hours in front of the IPTables manual just to setup a Firewall that keeps the "bad" people out.




Changelog:

Hi,
Donatas Glodenis provides KMyFirewall 1.1.1 and patched kdesudo packages for Ubuntu/Kubuntu at http://dg.lapas.info/share/paketai/ubuntu-gutsy/

thanks for his support!
greetz,
chris

---

Hi,
As reported by Donatas Gloden the installation process in version 1.1.0 is seriously broken - IT DOES NOT INSTALL A VALID SCRIPT!

So please Update to v1.1.1 that i've just released on sf.net if you are using 1.1.0!

---

Hi,
With great thanks to Donatas Glodenis here is a much better fix solving the "kdesu -t issue". Here are the instructions form his email:

The kdesudo version 2.1, available for the coming version of Ubuntu Hardy
Heron (8.4), already has the -t option implemented. You can build your own
kdesudo package for gutsy by following these steps:

1. Download these packages from the repositories:
$ wget http://archive.ubuntu.com/ubuntu/pool/main/k/kdesudo/kdesudo_2.1-0ubuntu1.dsc
$ wget
http://archive.ubuntu.com/ubuntu/pool/main/k/kdesudo/kdesudo_2.1.orig.tar.gz
$ wget
http://archive.ubuntu.com/ubuntu/pool/main/k/kdesudo/kdesudo_2.1-0ubuntu1.diff.gz

2. setup sources:
$ dpkg-source -x kdesudo_2.1-0ubuntu1.dsc

3. Build package:
$ cd kdesudo-2.1/
$ sudo apt-get build-dep kdesudo
$ dpkg-buildpackage -rfakeroot -uc -b

4. Install package
$ cd ../
$ sudo dpkg -i kdesudo*.deb

Here is the apt-get source for KMyFirewall and the patched KDEsudo

http://dg.lapas.info/share/paketai/ubuntu-gutsy/

greetings,
chris

---

Release of KMyFirewall 1.1.0

Well, it has been a while since the last release, almost 2 years ;)

Sorry for the slow progress until now, but i hope the new KMyFirewall 1.1.0 release will excuse the long waiting.

This release includes lots of cool new features (e.g. multi target configuration, remote installation etc.) and fixes all known bugs. Again the document format has changed a bit but i did my best to make it compatible with rule sets created using v1.0.x


Multi Target Configuration & Remote firewall control

With KMyFirewall 1.1.0 you are now able to define so called Targets (accessible in the MyNetwork View), those are the computers you like to manage using KMyFirewall.
After configuring a target (IP address and SSH port) you simply set it as the "Active Target" and edit it's rule set as you did for localhost. The only requirement is that the target allows SSH connections and has a bash shell installed.
With the help of KDE's KIO technology you can install, run, show configuration etc. on the remote host, as you did on localhost before.
All communication between KMyFirewall and the target is encrypted using SSH.


New Undo/Redo Engine

As consequence to the lots of trouble the current undo/redo implementation has made, i re-designed it and as result the engine is faster, more reliable and much easier to use as a developer.


Custom Protocols (Generic Interface)

This solves on of the most annoying problems of the Generic Interface. In KMyFirewall's settings dialog you now can define your own protocols.
So if you find any important protocol still missing, simply create it and if you like send it to chubinger_AT_irrsinnig_DOT_org so that i can add it for the next release. (For the future i plan to implement a KHotNewStuff service to allow online updates of the protocol library.)


Improved Auto Configuration

The auto configuration capabilities have been moved to a small bash script and therefore can also be used for remote targets. If your system is not detected correctly please send your configuration to chubinger_AT_irrsinnig_DOT_org so that i can add them to the auto configuration script.

So finally i just like to say have fun managing your firewalls using KMyFirewall 1.1.0
Feedback and burg reports are very welcome.

greetings,
Chris

----

Release of KMyFirewall 1.0.1

* Adding some more protocols to the Protocol library
* Fix spelling bug in Workstation template
* Small code cleanup
* Deleted old Parser and Wizrad files
* Fix rule index handling
* Allow insert of rules.
* Fix Rule renamed canceled bug
* cleanup interface add parameter to select the config part to show insted of different methods
* Add posibilty to export a package containing the scripts needed to install the ruleset on the system
* Add commandline parameter to define the GUI interface to startup with
* Fix chain log prefix saving bug
* Fix multiport ruleoption bug

-----

Release of KMyFirewall 1.0

Important: As the file format used to save the rulesets has changed, rulesets created with KMyFirewall < 1.0beta1 WILL NOT work, don't even try it!

Since the last stable release KMF has been completely rewritten in order to be even more flexible and on the other hand easier to use.

New plugin framework

Most parts of the application has been rewritten introducing a plugin framework that allows to add new IPTables rule option editors to be written within a few hours (well maybe days depends on the options complexity :).
This will allow us (and contributors) to easily implement the fast growing number of IPTables ruleoptions without the need of understanding the whole application.

The backend generating the IPTables rules itself has been extended to allow the registration of new rule options by defining them in an XML description file. For a detailed description about how to write such plugins have a look at the application handbook in the current CVS version.
So feel free to contribute plugins, there are lots of options still not implemented.

New Easy-To-Use platform independent interface

As I often got mails complaining about the to complex nature of KMF and the very limited possibilities the wizard provides i simply removed the wizard and implemented a completely new interface.


Features of the new Interface

As the new interface works on an abstract descrioption of the generated rules the new plugin structure allows us top implement script compilers that support other firewalling backends than just netfilter/iptables.

To support a new tool kit it is required to write a compiler and an installer plugin for the new framework. Currently just the iptables/linux compiler and installer is implemented. As with the rule option plugins of the IPTables interface it shouldn't bee too much work to develop those plugins.

IPTables vs. Generic interface

The main difference between those two interfaces is that the new Generic Interface is OS and toolkit independant while the IPTables interface is an improved version of the well known KMF GUI and therefore tight bound to the netfiler/iptables toolkit and can therefore only be used with Linux as operating system.


Why two different interfaces?

Especially when concerning security related applications you (as developer) need to decide if you like to build an application used by expert users (e.g. experienced system administrators) or if you like to provide a tool that everybody can handle.

It hasn't been an easy decision to implement one interface for each user group but after pondering about concepts to merge those two requirements into one interface we decided that it is much better to separate them.
This allows us to concentrate on the wishes and wanted features for each of the user groups.

---


Homepage Update

Some developer documentation has been added. Have a look ath the "Documentation" section to see whats new.

---

Uploaded Suse 9.2 rpms.
Thanks to Marcus for contributing those.

APT users may install from the following repository:

ftp://ftp.gwdg.de/pub/linux/suse/apt SuSE/9.2-i386 suser-tux

---



Updating links to www.rockersoft.org Fedora Core 1/2 rpms.
They should also work for FC3

---

Adding debian testing/ustable package contributed by Raphael Lechner

---

New homepage online!

I'm very happy to announce the availability of the new fresh designed KMyFirewall homepage.
The design and implementation was done by Anton Frennevi who also designed a new icon set for KMF.
Unfortuantely he won't have anymore time to work with us so a big thank you very much to him.

---

0.9.6.1 -> 0.9.6.2
Fixed rule creation bug in Wizard
Made adding of other devvice types then the defaults possible
Several small fixes

---

Rockersoft made packages for Fedora Core 1 available via their download server at:
http://www.rockerssoft.com/apt/fedora/1/en/i386/RPMS.rockerssoft/

Those packages are also available via an apt-get repository at:
http://www.rockerssoft.com/apt/fedora/1/en/i386/

Thanks a lot to the guys at Rockerssoft:
http://www.rockerssoft.com/forum/




LicenseGPL
(Source)
Donate
Send to a friend
Subscribe
Other  Apps  from theanimal666
Report inappropriate content



goto page: prev   1  2  3 

-

 Slackware problem

 
 by LocoMojo on: Oct 25 2006
 
Score 50%

I've always used Firestarter, but I recently kicked Gnome off my system seeing as I never use it and it just took up space on my disk.

Since I didn't have the necessary dependencies from Gnome for Firestarter I tried Guarddog for a few days, but I found it to be rather confusing to configure and use.

Today I tried KMyFirewall and I found it to be very easy and intuitive to use. However, I ran into a small problem when trying to install the firewall to my Slackware system. Though I told KyMyFirewall that I was using Slackware, it kept trying to install the scripts to /etc/init.d which is not present on a Slackware system. The path selection for /etc/init.d was grayed out and it wouldn't allow me to change it so I told KMyFirewall that I was using an LSB distribution which then allowed me to change the init.d path to /etc/kmyfirewall. However, even though I got my soft links in my /etc/rc.d directory, the firewall would not start up at boot time. I removed those soft links and created a new soft link called rc.firewall which pointed to /etc/kmyfirewall/kmyfirewall

That worked because Slackware's rc.inet2 script looks for an rc.firewall script in rc.d and if it finds one it issues a rc.firewall start command.

You may want to fix that so it will install on a Slackware system properly.

Also, the cups protocol is missing from the protocol library which was easy enough to fix by editing the kmfprotocollibrary.xml file. Seeing as cups is a common printing service you may want to include that protocol in the install.

Thanks for a great app, I'm pleased so far.

LocoMojo


Reply to this

-

 Re: Slackware proble

 
 by theanimal666 on: Nov 14 2006
 
Score 50%

I'll fix that in the next release but i cannot tell when this will happen a my tim eis quite limited at the moment.

greetings,
chris


If it compiles, commit to CVS.
If it links, ship to customer.
It it runs without bugs, ..., nah, never had that case.

Reply to this

-
.

 Can't accept smb

 
 by marcel83 on: Oct 30 2007
 
Score 50%

Hi.

When I try to start my firewall with smb accepted I get this error:

Clearing iptables (created by KMyFirewall)... Done.
Starting iptables (created by KMyFirewall)...
Loading needed modules... Done.
Create custom chains... Done.
Settup Rules in Table FILTER:
Create Rules for Chain: INPUT
Error: iptables v1.3.8: multiport needs `-p tcp', `-p udp', `-p udplite', `-p sctp' or `-p dccp'
Error: Try `iptables -h' or 'iptables --help' for more information.
Setting up Rule: SMB_tcp FAILED!

Execution failed
Exit(Code): 1

Does anyone else have this problem? Is there any way to fix it?

The only "solution" I've found so far is to install the firewall anyway and then manually fix the affected line in the /etc/kmyfirewall/kmyfirewall.sh script myself.

I already posted this at the forum at Sourceforge but as it doesn't seem to be very active I'm trying it here.

Thanks in advance.


Reply to this

-
.

 Re: Can't accept smb

 
 by marcel83 on: Oct 31 2007
 
Score 50%

Ok. I managed to fix this myself although I would consider it a hack.

I edited the kmfruleoption_protocol_option.xml and added the '-p tcp' and '-p udp' options to the "command"-attributes of the tcp_multiport_opt and udp_multiport_opt definitions. So it looks like this (for tcp as example):

<ruleoptiondefinition name="tcp_multiport_opt" guiName="TCP Multiport">
<option guiName="" command="-p tcp --match multiport" />
...

Still it would be nice if this could be fixed for a next release.

Best regards.


Reply to this

-

 Re: Re: Can't accept

 
 by theanimal666 on: Jan 21 2008
 
Score 50%

Hi,

This issue is fixxed in v1.1.0

greetz,
chris


If it compiles, commit to SVN.
If it links, ship to customer.
It it runs without bugs, ..., nah, never had that case.

Reply to this

-

 incoming ports

 
 by rumbelino on: May 10 2008
 
Score 50%

On generic setup, how can I set to allow specific incoming ports?

Thanks


Reply to this

-
.

 KDE4 version of KMyFirewall?

 
 by Oceanwaves on: Nov 12 2009
 
Score 50%

Hi,

I've switched to KDE4 recently and KMyFirewall is one of the last apps requiring KDE3.

Will there ever be a KDE4 version or was development of KMyFirewall stopped?

Oceanwaves


Reply to this

goto page: prev   1  2  3 

Add commentBack






-
-
Do you like or dislike Ubuntu Unity?
 Yes, unity is alien technology!
 It is less confusing than Gnome 3 default, shell.
 Granny thinks it is much more usable than Gnome 2
 Canonical is embarrasing itself with this split project
 Gnome 3 default shell is much better
 I dislike Unity, Gnome 3 default shell is alien technology!
 None of the above, I like the 2Gb for free and Apple alike behavior. Will post a comment instead

resultmore
 
 
 Who we are
Contact
More about us
Frequently Asked Questions
Register
Twitter
Blog
Explore
Apps
Jobs
Knowledge
Events
People
Updates on identi.ca
Updates on Twitter
Facebook App
Content RSS   
Events RSS   

Participate
Groups
Forum
Add App
Public API
About KDE-Apps.org
Legal Notice
Spreadshirt Shop
CafePress Shop
Advertising
Sponsor us
Report Abuse
 

Copyright 2003-2014 KDE-Apps.org Team  
All rights reserved. KDE-Apps.org is not liable for any content or goods on this site.
All contributors are responsible for the lawfulness of their uploads.
KDE and K Desktop Environment are trademarks of KDE e.V.