Closed Bug 1369566 Opened 7 years ago Closed 7 years ago

OSX firewall puppet support

Categories

(Infrastructure & Operations :: RelOps: Puppet, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: dividehex, Assigned: dividehex)

References

Details

Attachments

(3 files)

This really deserves a bug of its own.  OSX has a couple firewall layers,  the one we will be focusing on is the pf (packet firewall).
I'll be using t-yosemite-r7-393.test.releng.mdc1.mozilla.com for testing.
This is my first attempt at setting up a module for osx pf management.  It also setups up a roles and profile framework for build modular firewall rule definitions independent of which posix OS we are trying to manage.

The rules and network definitions are in no way meant to be exhaustive.  I've only setup a few roles/profiles to get the ball rolling for when we come together and start filling in the blanks.
Attachment #8879716 - Flags: review?(dhouse)
Attachment #8879716 - Flags: review?(dhouse) → review+
Blocks: 1379671
Blocks: 1379673
Depends on: 1386374
This adds support for OSX 10.7 to the pf module.  For the most part, there is not a big difference.

* pf.conf per osx major version
* Do not pass tcpdump sdterr to syslog since it is verbose on startup
Attachment #8893000 - Flags: review?(dhouse)
Attachment #8893000 - Flags: review?(dhouse) → review+
This ensure the pflog daemon actually runs via puppet and not just on boot.  Also, moved service to a proper name format.
Attachment #8893499 - Flags: review?(dhouse)
Attachment #8893499 - Flags: review?(dhouse) → review+
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: