Free automatic expiration software for linux

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.

Auto Contrast is a script-fu based on a technique by lylejk of dpreview.com that performs an entirely automatic contrast adjustment.

You may like the effect, dislike it, or not see a change, but its worth a try!

K5expire is a tool to complement a Kerberos/LDAP server combination.
It checks all kerberos principals per user in LDAP for password and/or account expiration and sends E-mails to the owner if they will expire in a preconfigured amount of time.
It started as a hack to emulate the behavior of expiration found in pam_unix and Windows, but I believe this method to be less intrusive because it does not delay the login process.
Enhancements:
- Support for XMLSensor output was added.

Xautolock monitors console activity under the X window system, and fires up a program of your choice if nothing happens during a user configurable period of time.

You can use this to automatically start up a screen locker in case you tend to forget to do so manually before having a coffee break.

TigerWiki is a wiki that provides password security, automatic backup pages when editing, easy custom templates, and more.
TigerWiki is less than 20 kilobytes large.
Enhancements:
- A security fix that prevented new pages from being created was removed.

mod_auth_tkt is an original mod_auth_tkt, with some improvements (inactivity timeout).
Main features:
- Some fixes from the original module.
- There were several little things that were not portable or just didnt work fine; it was also a good time for learning more about apache API and such.
- Expiration of authentication due to inactivity!
- Possibility of closing the session

Mail::DKIM::Signature module encapsulates a DKIM signature header.

CONSTRUCTORS

new() - create a new signature from parameters

my $signature = new Mail::DKIM::Signature(
[ Algorithm => "rsa-sha1", ]
[ Signature => $base64, ]
[ Method => "relaxed", ]
[ Domain => "example.org", ]
[ Headers => "from:subject:date:message-id", ]
[ Query => "dns", ]
[ Selector => "alpha", ]
);
parse() - create a new signature from a DKIM-Signature header
my $sig = parse Mail::DKIM::Signature(
"DKIM-Signature: a=rsa-sha1; b=yluiJ7+0=; c=relaxed"
);

Constructs a signature by parsing the provided DKIM-Signature header content. You do not have to include the header name (i.e. "DKIM-Signature:") but it is recommended, so the header name can be preserved and returned the same way in as_string().

Note: The input to this constructor is in the same format as the output of the as_string method.

METHODS

algorithm() - get or set the algorithm (a=) field

The algorithm used to generate the signature. Should be either "rsa-sha1", an RSA-signed SHA-1 digest, or "rsa-sha256", an RSA-signed SHA-256 digest.
See also hash_algorithm().

as_string() - the signature header as a string
print $signature->as_string . "n";

outputs

DKIM-Signature: a=rsa-sha1; b=yluiJ7+0=; c=relaxed

As shown in the example, the as_string method can be used to generate the DKIM-Signature that gets prepended to a signed message.
as_string_without_data() - signature without the signature data

print $signature->as_string_without_data . "n";

outputs

DKIM-Signature: a=rsa-sha1; b=; c=relaxed

This is similar to the as_string() method, but it always excludes the "data" part. This is used by the DKIM canonicalization methods, which require incorporating this part of the signature into the signed message.

body_count() - get or set the body count (l=) field

my $i = $signature->body_count;

Informs the verifier of the number of bytes in the body of the email included in the cryptographic hash, starting from 0 immediately following the CRLF preceding the body. Also known as the l= tag.

When creating a signature, this tag may be either omitted, or set after the selected canonicalization system has received the entire message body (but before it canonicalizes the DKIM-Signature).

body_hash() - get or set the body hash (bh=) field

my $bh = $signature->body_hash;

The hash of the body part of the message. Whitespace is ignored in this value. This tag is required.

When accessing this value, whitespace is stripped from the tag for you.

canonicalization() - get or set the canonicalization (c=) field

$signature->canonicalization("relaxed", "simple");

($header, $body) = $signature->canonicalization;

Message canonicalization (default is "simple/simple"). This informs the verifier of the type of canonicalization used to prepare the message for signing.
In scalar context, this returns header/body canonicalization as a single string separated by /. In list context, it returns a two element array, containing first the header canonicalization, then the body.

domain() - get or set the domain (d=) field

my $d = $signature->domain; # gets the domain value
$signature->domain("example.org"); # sets the domain value

The domain of the signing entity, as specified in the signature. This is the domain that will be queried for the public key.

expiration() - get or set the signature expiration (x=) field

Signature expiration (default is undef, meaning no expiration). The signature expiration, if defined, is an unsigned integer identifying the standard Unix seconds-since-1970 time when the signature will expire.

get_public_key() - fetches the public key referenced by this signature

my $pubkey = $signature->get_public_key;

Public key to fetch is determined by the protocol, selector, and domain fields.

hash_algorithm() - access the hash algorithm specified in this signature

my $hash = $signature->hash_algorithm;

Determines what hashing algorithm is used as part of the signatures specified algorithm.

For algorithm "rsa-sha1", the hash algorithm is "sha1". Likewise, for algorithm "rsa-sha256", the hash algorithm is "sha256". If the algorithm is not recognized, undef is returned.

headerlist() - get or set the signed header fields (h=) field

$signature->headerlist("a:b:c");

my $headerlist = $signature->headerlist;

my @headers = $signature->headerlist;

Signed header fields. A colon-separated list of header field names that identify the header fields presented to the signing algorithm.

In scalar context, the list of header field names will be returned as a single string, with the names joined together with colons. In list context, the header field names will be returned as a list.

identity() - get or set the signing identity (i=) field

my $i = $signature->identity;

Identity of the user or agent on behalf of which this message is signed. The identity has an optional local part, followed by "@", then a domain name. The domain name should be the same as or a subdomain of the domain returned by the domain method.

Ideally, the identity should match the identity listed in the From: header, or the Sender: header, but this is not required to have a valid signature. Whether the identity used is "authorized" to sign for the given message is not determined here.

method() - get or set the canonicalization (c=) field

Message canonicalization (default is "simple"). This informs the verifier of the type of canonicalization used to prepare the message for signing.

protocol() - get or set the query methods (q=) field

A colon-separated list of query methods used to retrieve the public key (default is "dns"). Each query method is of the form "type[/options]", where the syntax and semantics of the options depends on the type.

selector() - get or set the selector (s=) field

The selector subdivides the namespace for the "d=" (domain) tag.

data() - get or set the signature data (b=) field

my $base64 = $signature->data;
$signature->data($base64);

The signature data. Whitespace is automatically stripped from the returned value. The data is Base64-encoded.

prettify() - alters the signature to look "nicer" as an email header

$signature->prettify;

This method may alter the signature in a way that breaks signatures, so it should be done ONLY when the signature is being generated, BEFORE being fed to the canonicalization algorithm.

prettify_safe() - same as prettify() but only touches the b= part

$signature->prettify_safe;

This method will not break the signature, but it only affects the b= part of the signature.

timestamp() - get or set the signature timestamp (t=) field

Signature timestamp (default is undef, meaning unknown creation time). This is the time that the signature was created. The value is an unsigned integer identifying the number of standard Unix seconds-since-1970.

version() - get or set the DKIM specification version (v=) field

This is the version of the DKIM specification that applies to this signature record.