Login or Register to Ask a Question and Join Our Community


OS X Support RSS

Mac OS X 10.5 Leopard: About the Application Firewall

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Operating Systems OS X (Apple) OS X Support RSS Mac OS X 10.5 Leopard: About the Application Firewall
# 1  
Old 11-21-2008
Mac OS X 10.5 Leopard: About the Application Firewall
Mac OS X 10.5 Leopard includes a new technology called the Application Firewall. One of the basic purposes of a firewall is to control connections made to your computer from other computers on the network. In most firewall software, you must know the network ports and protocols an application uses to communicate, in order to control that application's network connections. Note: This article applies to the version of the Application Firewall included with Mac OS X 10.5.1 and later. Update to Mac OS X 10.5.1 or later if you have not yet done so. The Firewall in Leopard is an Application Firewall. This type of firewall allows you to control connections on a per-application basis, rather than a per-port basis. This makes it easier for less experienced users to gain the benefits of firewall protection and helps prevent undesirable applications from taking control of network ports that have been opened for legitimate applications. The Firewall applies to the Internet protocols most commonly used by applications, TCP and UDP. It does not affect AppleTalk. The Firewall may be set to block incoming ICMP "pings" by enabling Stealth Mode in the Advanced settings. Earlier ipfw technology is still accessible from the command line (in Terminal) and the Application Firewall does not overrule rules set with ipfw; if ipfw blocks an incoming packet, the Application Firewall will not process it. This article applies to the version of the Application Firewall included with Mac OS X 10.5.1 and later.

More from Apple OS X Support ...
Login or Register to Ask a Question

Previous Thread | Next Thread

3 More Discussions You Might Find Interesting

1. OS X (Apple)

Use a Serial Console with Mac OS X Leopard

I'm trying to use an old Commodore 128D as a terminal to access OS X's shell via a serial port. I've used 'screen' and 'zterm' to ensure the two machines are successfully interfaced. Instructions for opening up the serial console on other Unix-y operating systems don't work with OS X Leopard. ... (3 Replies)
Discussion started by: joecassara
3 Replies

2. OS X (Apple)

loading MAC X 5.0(leopard) on a X86 laptop

I want to install MAC X 5.x on my T60 Lenova laptop. I have the Original Mac X 5.0 installation media. I tried to install it on a blank hard disk in my laptop but it doesn't work. On the internet I found sites that offer torrent downloads but I can't use torrent downloads on my laptop. (Corp... (1 Reply)
Discussion started by: mndavies
1 Replies

3. Shell Programming and Scripting

mac backup script in leopard

Hi all I had a nice simple backup script on my mac running Tiger. I used an Automator 'Run Shell Script' command that loaded psync and backed up one directory on an external drive to a directory on another external drive. This was the command /usr/local/bin/runpsync 0 0 0... (1 Reply)
Discussion started by: Billy T
1 Replies
Login or Register to Ask a Question

LEARN ABOUT DEBIAN

fwb_ipf

fwb_ipf(1)							 Firewall Builder							fwb_ipf(1)

NAME

       fwb_ipf - Policy compiler for ipfilter

SYNOPSIS

       fwb_ipf [-vVx] [-d wdir] [-o output.fw] [-i] -f data_file.xml object_name

DESCRIPTION

       fwb_ipf is a firewall policy compiler component of Firewall Builder (see fwbuilder(1)). This compiler generates code for ipfilter. Compiler
       reads objects definitions and firewall description from the data file specified with "-f" option and generates ipfilter configuration files
       and firewall activation script.

       All  generated files have names that start with the name of the firewall object. Firewall activation script has extension ".fw" and is sim-
       ple shell script that flushes current policy, loads new filter and nat rules and then activates ipfilter.  IPFilter configuration file name
       starts  with  the  name	of  the  firewall object, plus "-ipf.conf".  NAT configuration file name also starts with the name of the firewall
       object, plus "-nat.conf". For example, if firewall object has name "myfirewall", then compiler will create  three  files:  "myfirewall.fw",
       "myfirewall-pf.conf", "myfirewall-nat.conf".

       The data file and the name of the firewall objects must be specified on the command line. Other command line parameters are optional.

OPTIONS

       -f FILE
	      Specify the name of the data file to be processed.

       -o output.fw
	      Specify output file name

       -d wdir
	      Specify	working  directory.  Compiler  creates	firewall activation script and ipfilter configuration files in this directory.	If
	      this parameter is missing, then all files will be placed in the current working directory.

       -v     Be verbose: compiler prints diagnostic messages when it works.

       -V     Print version number and quit.

       -i     When this option is present, the last argument on the command line is supposed to be firewall object ID rather than its name

       -x     Generate debugging information while working. This option is intended for debugging only and may produce lots of cryptic messages.

NOTES

       Support for ipf returned in version 1.0.1 of Firewall Builder

       Supported features:

       o      both ipf.conf and nat.conf files are generated

       o      negation in policy rules

       o      stateful inspection in individual rule can be turned off in rule options dialog. By default compiler adds "keep state" or  "modulate
	      state" to each rule with action 'pass'

       o      rule options dialog provides a choice of icmp or tcp rst replies for rules with action "Reject"

       o      compiler adds flag "allow-opts" if match on ip options is needed

       o      compiler can generate rules matching on TCP flags

       o      compiler can generate script adding ip aliases for NAT rules using addresses that do not belong to any interface of the firewall

       o      compiler	always	adds  rule  "block quick all" at the very bottom of the script to ensure "block all by default" policy even if the
	      policy is empty.

       o      Address ranges in both policy and NAT

       Features that are not supported (yet)

       o      negation in NAT

       o      custom services

       Features that won't be supported (at least not anytime soon)

       o      policy routing

URL

       Firewall Builder home page is located at the following URL: http://www.fwbuilder.org/

BUGS

       Please report bugs using bug tracking system on SourceForge:

       http://sourceforge.net/tracker/?group_id=5314&atid=105314

SEE ALSO

       fwbuilder(1), fwb_ipt(1), fwb_pf(1)

FWB
																	fwb_ipf(1)