Table of Contents
- Module Description - What the module does and why it is useful
- Setup - The basics of getting started with tripwire
- Usage - Configuration options and additional functionality
- Reference - An under-the-hood peek at what the module is doing and how
- Limitations - OS compatibility, etc.
- Development - Guide for contributing to the module
Tripwire Puppet module objective is to automate the process of installing and connecting a Tripwire client to the Tripwire master
Tripwire module was designed to be applied to Puppets base_linux_install manifest, this was simply done with an include tripwire in the base_linux class. However you can load the module into your modulepath and declare the class through Puppet web console.Goto the Puppet console, select the Tripwire profile class, apply it to any RedHat Linux server have Tripwire installed and communicating with a Tripwire master
To retrieve the public module code , please clone git clone firstname.lastname@example.org:autostructure/tripwire.git The private data will need to be designed accordingly for your Organizations purpose
What tripwire affects
Tripwire application monitors pre defined directories/files, this monitors the files / directories for any changes, this will help an organization determine if these changes were scheduled or unscheduled
Setup Requirements OPTIONAL
Beginning with tripwire
In order to pull the public code into your Puppet Infrastructure please add the following line to your Puppetfile mod "autostructure/tripwire"
Within the Tripwire profile that can be seen by querying the class in the Puppet console $twip This parameter is the IP address to the Tripwire Master server to connect with Integer[0, 65535] $twtripport This is the port to connect to the Master Tripwire server with String $pass This is the passcode needed to make a successful connection to the Master te_agent_8.4.2_en_linux_x86_64/te_agent.bin <--- This is the file downloaded from a trusted repo, this file will install tripwire agent on the Client
Here, list the classes, types, providers, facts, etc contained in your module. This section should include all of the under-the-hood workings of your module so people know what the module is touching on their system but don't need to mess with things. (We are working on automating this section!)
This is where you list OS compatibility, version compatibility, etc.
Since your module is awesome, other users will want to play with it. Let them know what the ground rules for contributing are.
Release Notes/Contributors/Etc Optional
If you aren't using changelog, put your release notes here (though you should consider using changelog). You may also add any additional sections you feel are necessary or important to include here. Please use the