Free classified software for linux

LiquidClassifiedsXML project is a classified ad web service client available for PHP-Nuke and PostNuke.
All ads are pooled in a centralized database so that many small Web sites can combine their marketing power to have, in effect, the classified ad system of a large Web site.
After you register your site with LiquidMarkets, each site that implements LCX 1.1.1 or higher will automatically link to your site.
Enhancements:
- The "Business" category was removed.
- The "Pets" category was split into "Pets: Dogs" and "Pets: Other".

morigin email classifier is a filter that classifies and tags email messages based on the DNS information of the system submitting the mail to your organization.

morigin email classifier can then be used to improve upon existing spam filters such as SpamAssassin.

Mail::Classifier::GrahamSpam is a spam classification tool based on Paul Grahams algorithm.

SYNOPSIS

use Mail::Classifier::GrahamSpam;
$bb = Mail::Classifier::GrahamSpam->new();
$bb->bias( NOTSPAM, 2);
$bb->train( { spam.mbox => SPAM, notspam.mbox => NOTSPAM } );
my ($cat, $prob) = $bb->score( $msg );

ABSTRACT

Mail::Classifier::GrahamSpam - spam classification based on Paul Grahams algorithm

This class is a specific implementation of a Mail::Classifier that uses Naive Bayesian methods for associating messages with a category. The specific implemenation is based on the article "A Plan for Spam" by Paul Graham (thus the name).
For classic Graham, make sure to set bias on non-spam to 2.
While this class was designed to classify spam and non-spam, there is no underlying limitation that only two categories be used and thus it may be used for more general purposes as well. (And should perhaps be renamed in a subsequent release.) For example, we might call

$bb->train ({ perl.mbox => PERL,
java.mbox => JAVA,
php.mbox => PHP });

in order to train the classifier to identify other categories of mail.

File is the open source implementation of the file command used on almost every free operating system (OpenBSD, Linux, FreeBSD, NetBSD) and also on systems that use free software (including OS/2, DOS, MS Windows, etc.).

The file command, if youre not familiar with it, is a command-line tool that tells you in words what kind of data a file contains. Unlike MS-Windows, UNIX and other systems dont rely on filename extentions to tell you the type of a file, but look at the files actual contents. This is, of course, more reliable, but requires a bit of I/O.

The original file command shipped with Bell Labs UNIX but was unavailable in source form to the masses before Ians reimplementation.

This file command (and magic file) was originally written by Ian Darwin (who still contributes occasionally) and is now maintained by a group of developers lead by Christos Zoulas.

Whos using it?

Every known BSD distribution (FreeBSD, NetBSD, OpenBSD, Darwin/Mac OS X, etc)
Every known Linux distribution
The Apache httpd server mod_mime_magic module uses the file commands innards to make file type guessing more reliable under Apache HTTPD.

ASSP is the best SPAM fighting weapon that the world has ever known! When it comes to killing SPAM nothing is as deadly as an ASSP!
Main features:
- Easy browser-based setup (optional).
- Uses your existing message transport and existing SMTP server.
- Works with Sendmail, qmail, Postfix, Imail, Exchange, Courier, Mercury, Lotus Notes, and all other standard SMTP servers.
- Runs on Linux, Unix, Windows, OS X, OS/2, and more.
- Automatically customizes to your sites unique email profile.
- Automatic whitelist -- noone you email will ever be blocked.
- Early Sender validation -- Kills most spam before it ever reaches the server.
- Senders receive immediate notification if mail is blocked but no erroneous bounces are ever generated.
- Redlist keeps an address off the whitelist.
- No-processing addresses pass through.
- Makes use of honeypot type spambucket addresses to automatically recognize spam and update your spam database.
- Bayesian filter intelligently classifies email into spam and non-spam.
- Supports additional site-defined regular expressions to identify spam or non-spam email.
- Can optionally block all non-whitelisted email (for anti-spam zelots).
- Mime encoded and other camouflaged spam is also recognized.
- Automatically maintains the spam and non-spam databases.
- Accepts whitelist submissions and spam error reports by authorized email.
- Optionally rejects executable attachments from non-whitelisted (or all) addresses.
- Free (as in speech) software -- Licensed under the GPL.
- Practically no maintenance required.
- Active user community and email list for support questions.
- Source code included if you need to customize your installation.
- Runs as a service in Windows NT / 2000.
- Optionally blocks no mail but adds an email header and/or updates the message subject.
- Optionally uses community-based spam statistics to identify hosts that are likely to send spam or non-spam mail.
- In *nix environments can switch to non-root user. Also supports chroot jail.
- Individual users can be configured to receive all mail.
- Shows detailed analysis of spam rating process for specific messages.
- Option to forward a copy of every rejected mail to an address.
- Can block spam-bombs (when spammers forge your domain in the from field).
- Keeps spam statistics for your site.
- Detailed documentation.
- Can listen on more than one smtp port.

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.

pam_passwdqc is a simple password strength checking module for PAM-aware password changing programs, such as passwd.

In addition to checking regular passwords, it offers support for passphrases and can provide randomly generated ones. All features are optional and can be (re-)configured without rebuilding.

This module should be stacked before your usual password changing module (such as pam_unix or pam_pwdb) in the password management group (the "password" lines in /etc/pam.d/passwd or /etc/pam.conf). The password changing module should then be told to use the provided new authentication token (new password) rather than request it from the user.

Theres usually the "use_authtok" option to do that. If your password changing module lacks the "use_authtok" option or its prompts are inconsistent with pam_passwdqcs, you may tell pam_passwdqc to ask for the old password as well, with "ask_oldauthtok". In that case the option to use with the password changing module is "use_first_pass".

Theres a number of supported options which can be used to modify the behavior of pam_passwdqc (defaults are given in square brackets):

min=N0,N1,N2,N3,N4 [min=disabled,24,12,8,7]

The minimum allowed password lengths for different kinds of passwords and passphrases. The keyword "disabled" can be used to disallow passwords of a given kind regardless of their length. Each subsequent number is required to be no larger than the preceding one.

N0 is used for passwords consisting of characters from one character class only. The character classes are: digits, lower-case letters, upper-case letters, and other characters. There is also a special class for non-ASCII characters which could not be classified, but are assumed to be non-digits.

N1 is used for passwords consisting of characters from two character classes which do not meet the requirements for a passphrase.

N2 is used for passphrases. A passphrase must consist of sufficient words (see the "passphrase" option below).

N3 and N4 are used for passwords consisting of characters from three and four character classes, respectively.

When calculating the number of character classes, upper-case letters used as the first character and digits used as the last character of a password are not counted.

In addition to being sufficiently long, passwords are required to contain enough different characters for the character classes and the minimum length they have been checked against.

max=N [max=40]

The maximum allowed password length. This can be used to prevent users from setting passwords which may be too long for some system services.

The value 8 is treated specially: with max=8, passwords longer than 8 characters will not be rejected, but will be truncated to 8 characters for the strength checks and the user will be warned. This is to be used with the traditional DES-based password hashes, which truncate the password at 8 characters.

It is important that you do set max=8 if you are using the traditional hashes, or some weak passwords will pass the checks.

passphrase=N [passphrase=3]

The number of words required for a passphrase, or 0 to disable the support for user-chosen passphrases.

match=N [match=4]

The length of common substring required to conclude that a password is at least partially based on information found in a character string, or 0 to disable the substring search. Note that the password will not be rejected once a weak substring is found; it will instead be subjected to the usual strength requirements with the weak substring removed.

The substring search is case-insensitive and is able to detect and remove a common substring spelled backwards.

similar=permit|deny [similar=deny]

Whether a new password is allowed to be similar to the old one. The passwords are considered to be similar when there is a sufficiently long common substring and the new password with the substring removed would be weak.

random=N[,only] [random=42]

The size of randomly-generated passphrases in bits (24 to 72), or 0 to disable this feature. Any passphrase that contains the offered randomly-generated string will be allowed regardless of other possible restrictions.

The "only" modifier can be used to disallow user-chosen passwords.

enforce=none|users|everyone [enforce=everyone]

The module can be configured to warn of weak passwords only, but not actually enforce strong passwords. The "users" setting will enforce strong passwords for invocations by non-root users only.

non-unix []

Normally, the module uses getpwnam(3) to obtain the users personal login information and use that during the password strength checks. This behavior can be disabled with the "non-unix" option.

retry=N [retry=3]

The number of times the module will ask for a new password if the user fails to provide a sufficiently strong password and enter it twice the first time.

ask_oldauthtok[=update] []

Ask for the old password as well. Normally, pam_passwdqc leaves this task for subsequent modules. With no argument, the "ask_oldauthtok" option will cause pam_passwdqc to ask for the old password during the preliminary check phase. With "ask_oldauthtok=update", pam_passwdqc will do that during the update phase.

check_oldauthtok []

This tells pam_passwdqc to validate the old password before giving a new password prompt. Normally, this task is left for subsequent modules.

The primary use for this option is when "ask_oldauthtok=update" is also specified, in which case no other module gets a chance to ask for and validate the password. Of course, this will only work with Unix passwords.

use_first_pass []
use_authtok []

Use the new password obtained by modules stacked before pam_passwdqc. This disables user interaction within pam_passwdqc. With this module, the only difference between "use_first_pass" and "use_authtok" is that the former is incompatible with "ask_oldauthtok".

Scalar::Number is a Perl module with numeric aspects of scalars.

SYNOPSIS

use Scalar::Number qw(scalar_num_part);

$num = scalar_num_part($scalar);

use Scalar::Number qw(sclnum_is_natint sclnum_is_float);

if(sclnum_is_natint($value)) { ...
if(sclnum_is_float($value)) { ...

use Scalar::Number qw(sclnum_val_cmp sclnum_id_cmp);

@sorted_nums = sort { sclnum_val_cmp($a, $b) } @floats;
@sorted_nums = sort { sclnum_id_cmp($a, $b) } @floats;

This module is about the numeric part of plain (string) Perl scalars. A scalar has a numeric value, which may be expressed in either the native integer type or the native floating point type. Many values are expressible both ways, in which case the exact representation is insignificant. To fully understand Perl arithmetic it is necessary to know about both of these representations, and the differing behaviours of numbers according to which way they are expressible.
This module provides functions to extract the numeric part of a scalar, classify a number by expressibility, and compare numbers across representations.