Free specifies software for linux

pam_siegho is a pam module that helps to defend your computer by closing the login prompts for visitors that repeatedly try to log in unsuccesfully.

Installation:

Just run configure and do the ordinary "make install". Differences between platforms will automatically be handled by the configure script. Let me know if its not.

Usage:

pamtester requires at least three arguments to operate. The first argument is "service", which provides the name of the service. The second one is "user", which provides the name of the user to handle with PAM. The last one is "operation", which specifies the operation for PAM to perform.

Operation may be specified more than once. In that case the operations are done
in the order of occurrence.

Any operation may also be followed by the option flags that are provided between the pair of parenthesis. Flags are all named and combinable or inversible with bitwise operators; "|" (OR), "&" (AND), "^" (XOR) and "~" (NOT) are accepted.

The list of allowed options is shown below:

- PAM_SILENT

- PAM_DISALLOW_NULL_AUTHTOK

- PAM_ESTABLISH_CRED

- PAM_REINITIALIZE_CRED

- PAM_REFRESH_CRED

- PAM_CHANGE_EXPIRED_AUTHTOK

Additional authentication information such as the name of the remote user, the remote host and the tty can be supplied via -I (--item) option.

The following types of information are supported:

- service

- user

- prompt

- tty

- ruser

- rhost

Sparklines are intense, simple, wordlike graphics.
Theres a PHP library for producing sparklines, and even a sparkline web service, but I wanted something I could use to generate sparklines in both Java and JSTL (and I thought it would be a fun project). (Its also worth checking out Whys minimalist python sparklines, which encode the image data directly in the HTML as a data: URI [this library allows you to encode the images as using either data: format or javascript: format (supported by IE) in JSTL])
JSTL examples
< %@ taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c" % >
< %@ taglib prefix="spark" uri="http://www.representqueens.com/taglibs/spark" % >
< c:set var="test" value="5, 35, 22, 19, 16, 10, 4, 33, 9, 12, 27, 36, 22" / >
< img src="< spark:bar name="test" color="red" / >" / >
will produce:
(I think the default size might be a little large).
The "name" attribute specifies the key to find the data (Uses JspContext.findAttribute). It expects the value to be either a List , a Number[], or a String of comma separated int values. Its the only manditory attribute.
The other attributes are width, height, spacing, color, highColor, lastColor, output. You can replace "bar" with "line" to get a linegraph (note: highColor and lastColor are currently not supported for line graphs).
The color attributes can either be a color name (a field name from java.awt.Color), or a HTML hex color (e.g. #ff0000 for red).
Enhancements:
- This release properly URL encodes parameters for server generated sparklines.
- This fixes an issue when using hex specified image colors.
- The tag parameter "background" has been added as a workaround for IE6 PNG transparency.

DBIx::Wrapper::Config Perl module allows the use of a configuration file in XML specifying information required to connect to databases using DBIx::Wrapper.

This way, your database connection specifications can be kept in one place.

Each "db" element specifies a key/name for the database connection, which should be passed as the $db_key argument to connect() in order to connect to that database.

The "db" elements children specify the dsn, authentication, and attribute information. dbi:mysql:database=test_db;host=example.com;port=3306 test_user test_pwd test_user test_pwd connect($db_key, $conf_path, %dbix_wrapper_attrs) Return a DBIx::Wrapper object connected to the database specified by $db_key in the file at $conf_path.

%dbix_wrapper_attrs is the optional 5th argument to DBIx::Wrappers connect() method, specifying handlers, etc. The file specified by $conf_path should be in the format specified in the DESCRIPTION section of this document.

Installation:

perl Makefile.PL
make
make test
make install

Sopeq is a stealth ingress and egress filtering firewall for IPTables with an easy to configure rules file.
Sopeq project can be used to configure even the slightest details of IPTables with just a minor change in the rules file.
Sopeq can be used to configure even the slightest details of IPTables with just a minor change in the rules file.
Argument Descriptions:
accept/droplog/rejectlog/log - This specifies what to do if a packet matches the
criteria given. "accept" accepts the packet, "droplog" drops and logs
the packet with given "lbl" variable (see section "vars" below),
"rejectlog" rejects and logs the packet with given "lbl" variable, and
"log" ONLY logs the packet with given "lbl" variable. Hmmm, I think I
see an eerie pattern emerging here...
if - This specifies what network interface the packet is travelling over.
This can also match packets NOT travelling over an interface by simply
adding an exclamation mark [!] before it. There should NOT be a space
after the exclamation mark like iptables requires.
in/out - This specifies whether the rule is looking at packets coming in or
packets going out. "in" should be used for most server rules, and
"out" should be used for most application rules. The rule is made by
adding the appropriate INPUT and OUTPUT rules in iptables to accept the
response to the packet as well.
This field can be left blank, but only if the "ports" field is blank as
well. This type of rule would allow all packets from a specific IP or
something to that extent.
tcp/udp/icmp - This is pretty self explanatory, it specifies the protocol of a
packet, IE: TCP, UDP, or ICMP. You can leave this blank to match all
protocols.
IPs - This specifies what specific IP addresses to allow for the rules. You
can leave this field blank to match all IPs. You can specify multiple
IP addresses by separating them with a comma, and/or use IP ranges.
Two methods of IP ranges are supported. The "1.2.3.0/24" method and
the "1.2.3.4-1.2.3.10" method. You can combine IPs and IP ranges in
the same rule with the comma delimeter.
Examples:
1.2.3.4
11.22.33.0/24
123.45.67.3-123.45.67.90
1.2.3.4,5.6.7.8,11.22.33.0/24,123.45.67.3-123.45.67.90
ports - This specifies which ports to allow on. Multiple ports can be
specified by separating them with a comma. If you leave the field
blank, it allows on all ports.
extras - This specifies extra options added onto the end of the rule. The field
is divided into two sections with a "|", which separates the extras for
the INPUT table with the extras from the OUTPUT table (in that order).
In order to have a space in the extras, you have to put the whole thing
in quotes (currently, you can only use double quotes, not single
quotes). These extras are just standard iptables options, so if you
want a list, view the iptables manual.
Examples:
No extras for the INPUT rule, "-m owner --uid-owner 0" for the
OUTPUT rule:
"|-m owner --uid-owner 0"
No extras for the INPUT rule, "-m owner --cmd-owner httpd" for the
OUTPUT rule:
"|-m owner --cmd-owner httpd"
vars - The syntax of a var field is:
varname="value"
Enhancements:
- The "version" option was added.
- A minor alteration was done in the way iptables was called.
- Minor code cleanup was done.

Parse::Binary::FixedFormat::Variants is a Perl module to convert between variant records and hashes.

Parse::Binary::FixedFormat supports variant record formats. To describe a variant structure, pass a hash reference containing the following elements to new. The object returned to handle variant records will be a Parse::Binary::FixedFormat::Variants.

Chooser

When converting a buffer to a hash, this subroutine is invoked after applying the first format to the buffer. The generated hash reference is passed to this routine. Any field names specified in the first format are available to be used in making a decision on which format to use to decipher the buffer. This routine should return the index of the proper format specification.

When converting a hash to a buffer, this subroutine is invoked first to choose a packing format. Since the same function is used for both conversions, this function should restrict itself to field names that exist in format 0 and those fields should exist in the same place in all formats.

Formats

This is a reference to a list of formats. Each format contains a list of field specifications.

For example:
my $cvt = new Parse::Binary::FixedFormat {
Chooser => sub { my $rec=shift;
$rec->{RecordType} eq 0 ? 1 : 2
},
Formats => [ [ RecordType:A1 ],
[ RecordType:A1, FieldA:A6, FieldB:A4:4 ],
[ RecordType:A1, FieldC:A4, FieldD:A18 ] ]
};
my $rec0 = $cvt->unformat("0FieldAB[0]B[1]B[2]B[3]");
my $rec1 = $cvt->unformat("1FldC");

In the above example, the Chooser function looks at the contents of the RecordType field. If it contains a 0, format 1 is used. Otherwise, format 2 is used.

Parse::Binary::FixedFormat::Variants can be used is if it were a Parse::Binary::FixedFormat. The format and unformat methods will determine which variant to use automatically. The blank method requires an argument that specifies the variant number.

cvsgdiff uses tkdiff or mgdiff to graphically display diffs between CVS revisions of a file in your sandbox. cvsgdiff is basically a graphical version of "cvs diff".

If given no arguments, cvsgdiff will launch the graphical diff program once for every modified file in the current directory.

If given one or more filenames as arguments, cvsgdiff diplays the diffs of each file. If given a revision, cvsgdiff will display the diffs between the file in your sandbox and the BASE revision in CVS. If given two revisions, cvsgdiff will display the diffs between the two revisions in CVS for the given file. The files in your sandbox are not touched.

cvsgdiff works by checking out the specified (or defaults to BASE) revision of the specified file(s) into your tmp directory and then launches a graphics diff program to display the differences.

The files in your tmp directory are then removed when you exit the graphical diff program. cvsgdiff currently supports tkdiff and mgdiff. It first checks the environment variable GDIFF. If it is set, that program will be tried first. If the GDIFF environment variable specifies an absolute path but does not exist, cvsgdiff will then look for tkdiff and mgdiff.

Grid-Split plugin splits an image into several images.

You specify number of rows and columns and the files are saved to jpeg, gif or png.