Free automatic configuration software for linux

NACE is a generic query engine used to automatically create host and service definitions for hosts on the network.

It is intended to be used in a shell script at regular intervals by an experienced Nagios administrator to perform a query against the supplied host list. It then creates host and service definitions using the parameters supplied in the query.

Automatic Firewall is a script that will automatically configure a firewall. If you are a broadband or dial-up user who doesnt have a firewall script, you need to get one to protect yourself. AutoFW is made to help you do that with no efforts.
Many people when connecting to the internet need a firewall script made for them so they can surf the net without being susceptible to various attacks. Most, if not all (until now :-), of the existing scripts are written for a large range of requirements and require some tweaking to make them work for a specific user. However many users do not know which parameters to fill in the script config file.
AutoFW intends to provide a simple firewall script that you just need to fire and forget. You make sure to run it on computer start-up or just before connecting to the net, and it will detect network condition and setup appropriate firewall rules for you.
In order to be "smart" AutoFW has to be limited, the current scope of AutoFW are standard broadband connections, it will also cover dial-up users and stand-alone servers.
AutoFW works only for Linux IPTables firewall and needs the iptables utility to update the firewall, it also needs the ifconfig utility, both of these are available on any standard install of a GNU/Linux machine.
AutoFW also needs the ip program which is part of the iproute2 package, sometimes also called iproute. It is available as a package for any standard GNU/Linux install, not it might not be installed in your particular.
There are two parts that do automatic detection, one is for interfaces and IPs and the other is for open listening ports.
The interface part looks at all the active interfaces in the machine and classifies them between internal and external. It does that by looking at the IPv4 address of the device. If it is one of:
127.0.0.0/8
10.0.0.0/8
172.16.0.0/12
192.168.0.0/16
it is considered to be an internal IP and thus an internal interface, otherwise it is an external IP and thus an external interface. There is no handling of an interface with both an internal and an external IP on it.
The listening ports are scanned for a known port and the accompanying known program name that binds to that port, known ports are opened later in the configuration stage.
The configuration itself is very simple for now, without many of the bell and whistles that exist in other scripts, but it works for the basic needs and provides adequate protection.
Enhancements:
- Internal systems are now protected, as well as servers and NAT gateways.

Emacs Configuration Framework is a versatile configuration package for Emacs. It is meant for users whose Emacs configuration has become so complex that it appears to be unmanageable.
It enables you to write and load the configuration for individual Emacs packages in pieces. You can use it to setup some autoloads for a package when you start Emacs and then do extra configuration after the package has loaded.
This speeds up your Emacs startup without compromising your ability to do complicated things.
Enhancements:
- This release adds a new rc.d/lang directory.
- Modes added: speedbar, semantic, cedet, and ecb.

SPOPS::Manual::Configuration is a description of variables used in the SPOPS configuration process.

These are variables used in all SPOPS implementations. The name of the variable is the key used in the configuration hashref.

Here is a fairly minimal example of a configuration hashref:

1: my $spops = {
2: news => {
3: class => My::News,
4: isa => [ qw/ MyApp::Datasource SPOPS::DBI::Pg SPOPS::DBI / ],
5: rules_from => [ My::DiscoverField ],
6: code_class => [],
7: field_discover => yes,
8: base_table => news,
9: id_field => news_id,
10: increment_field => 1,
11: no_insert => [ news_id ],
12: no_update => [ news_id ],
13: },
14: };

Fontconfig is a library for configuring and customizing font access.

Font Configuration Library contains two essential modules, the configuration module which builds an internal configuration from XML files and the matching module which accepts font patterns and returns the nearest matching font.

The configuration module consists of the FcConfig datatype, libexpat and FcConfigParse which walks over an XML tree and ammends a configuration with data found within. From an external perspective, configuration of the library consists of generating a valid XML tree and feeding that to FcConfigParse.

The only other mechanism provided to applications for changing the running configuration is to add fonts and directories to the list of application-provided font files.

The intent is to make font configurations relatively static, and shared by as many applications as possible.

It is hoped that this will lead to more stable font selection when passing names from one application to another. XML was chosen as a configuration file format because it provides a format which is easy for external agents to edit while retaining the correct structure and syntax.

Font configuration is separate from font matching; applications needing to do their own matching can access the available fonts from the library and perform private matching.

The intent is to permit applications to pick and choose appropriate functionality from the library instead of forcing them to choose between this library and a private configuration mechanism.

The hope is that this will ensure that configuration of fonts for all applications can be centralized in one place. Centralizing font configuration will simplify and regularize font installation and customization.

System Configuration Collector in short SCC, collects configuration data of systems in snapshots. The structure of the snapshot allows SCC to compare a snapshot with the previous one and detect changes in the configuration.
Upon detecting changes, scc adds the differences to a logbook. The snapshot and the logbook are converted to HTML for local inspection. Optionally, the SCC-files can be send to a system running the SCC server software. On the server, summaries of the SCC-data are generated and search/compare operations on the snapshots and logbooks are available via a web-interface.
The logbook is a starting point in case a system "suddenly" does not work correctly and the administrator is wondering what he/she has changed in the last weeks or months. As most of us know by experience, configuration changes can have accidental side-effects on (other) systems.
By examining the entries in the logbooks and considering the consequences, the cause of an actual problem might be found more easily than by just trying to remember the changes that were performed.
The snapshots can be used to compare the configuration of two systems. Imagine systems, that are supposed to be identical, but behave differently. Comparing parts of the snapshots of the two systems can indicate the cause of the difference in behavior.
Enhancements:
- The DIV tags in the HTML was corrected.
- Directory data/transfer was created to avoid errors in scc-pull. cpu-speed for SunOS was added.
- The machinfo variable is now initialized.
- The determination of local filesystems on Linux was corrected.
- Squid classification was corrected.

Configures your application for use within the Department of Defense.
Main features:
- urns on auto-updates
- Imports DoD Root Certificates
- Setup of CAC Reader driver
- Clarifies SSL error when Common Access Card (smartcard) not present (Firefox)
- Indicate when using trusted domain websites (.mil), similar to SSL (Firefox)
- Redirect to HTTPS when HTTP connection fails (Firefox)
- Sets up DoD LDAP Address Book (Thunderbird)
- Turns off image loading and javascript (Thunderbird)
- Setup of mail signing (Thunderbird)
- Looks at mail headers and warns if mail originates from outside of trusted domain (.mil) (Thunderbird)
Root certificates can be verified upon install by clicking on the View option. The fingerprints and other information can be verified at https://crl.gds.disa.mil.

The Configuration File Library (CFL) is a collection of routines for manipulating configuration files. The project is a portable library fully written from scratch in pure ANSI C.

It is designed to offer for C programmers common routines for manipulating configuration text files.