Free responsible use software for linux

Simple Backup is a shell script to create basic backups using tar, grep, sed, and bash.

Simple Backup works by using a file that contains the folders to be backed up and a file that contains expressions to exclude certain folders/files.

Usage: backup.sh < backuplist > < excludelist >

Free to use at your own risk. The author cant be held responsible for any side effects
of using this software. Use at your own risk.

IRC-Chess project is a 2-player chess game for IRC which turns a computer into an IRC chess bot.

It consists of a Java chess server, with frontend scripts to convert an IRC client into a chess bot. Players then communicate with the bot using standard IRC commands, and dont require any special software to play.

Frontend scripts are available for IRSSI and X-Chat.

The client is merely responsible for interpreting this data and displaying it. In this way, porting the system to a variety of IRC clients is very simple, since
the client script will be short, and effectively contain no code specific to the game being played.

In other words, the Java part is smart. The script is dumb and is just there to make things look pretty.

This idea works. Currently, client scripts have been designed for RSSI and XChat. Since both these programs use Perl for scripting, the scripts are practically identical, with a few client specific modifications.

Porting this script to other IRC clients shouldnt be too much of a hassle, since its just the frontend thats ported, not the chess game itself. Anyone wanting to create frontend scripts for other IRC clients, please feel free to do so.

The PROTOCOL file describes exactly what needs to be done.

Postfix-policy is a policy server that uses ServerKit to achieve a high level of performance and scalability for Postfix servers.

This project is ideal for use with large mail systems utilizing Postfix for MX duties and MySQL for the management of accounts with basic policy needs.

Usage:

It is advised that you read the ServerKit documentation before trying to use this module, as most of the basic usage is simply using ServerKit, nothing specific to this module.

You will probably want to use the included ServerKit personality as a starting point, found in the source archive as a directory named "personality". Within the personality you will find a "c11n" file, a "modules" subdirectory, and a "svsdir" subdirectory.

The "c11n" file is a ServerKit configuration file, you will need to at least modify the database settings so ServerKit can successfully communicate with your database system. Another configuration value that you will definitely have to set is "action_query_format_string".

The "action_query_format_string" is the SQL query postfix-policy will use to retrieve an action to send back to Postfix in response to policy delegation requests. See the Configuration section for a list of supported substitutions for use in the format string.

You are responsible for creating a query that is compatible with your mail system database schema, and ensuring that the query will:

1. return an empty set for invalid recipients
2. return a valid action string when not returning an empty set

For an explanation of valid policy action responses, see the access(5) manual reference from Postfix, youre interested in the *ACTIONS sections

PHLAK is a modular live security Linux distribution. PHLAK comes with two light guis (fluxbox and XFCE4), many security tools, and a spiral notebook full of security documentation. PHLAK is a derivative of Morphix, created by Alex de Landgraaf.
PHLAK is distributed freely. Some of the software included with PHLAK may not be GPL/GNU but can be distributed freely.
The developers of PHLAK express no warranty of any kind. Creators of PHLAK are not responsible or liable for an damages, criminal activity, misuse, or misrepresentations of PHLAK. USE AT YOUR OWN RISK!
Enhancements:
- removed XPDE and XFCE4
- removed security documentation
- removed all under /usr/share/doc/
- removed other unnecessary packages
- added iDesk to fluxbox
- updated fluxbox menus
- upgraded all applicable packages
- added usb modules to linuxrc script in miniroot.gz and new path for usb booting
- updated grub menu.lst, options.lst, and lang.lst files
- updated grub message
- updated bootsplash
- removed debian orphan packages
- purged all removed package data
- cleaned up minimod
- removed unnecessary files from base module
- modified usb pen drive install script for PHLAK compatibility
- modified PHLAK Security Panel tools and Control Panel tools

This is a library for making bubbling meters like the original bubbling load monitor.

The library accepts numbers as input for the different visualizations (water-level, color, amount of bubbles, amount of growth from the bottom, whether something is floating in the water).

It can then render a picture of it that you are responsible for passing to the screen (or whatever you want to do with it). As long as you render an image at least 10 times per second, the animation will be smooth.

Libbubblemon is intended to be entirely widget set independent, so you should be able to use it with your favourite desktop environment. If you find something that binds it to any certain platform, report it on the mailing list and it will be fixed.

pam_shield is a PAM module that uses iptables to lock out script kiddies that probe your computer for open logins and/or easy guessable passwords. The project is meant as an aid to protect public computers on the open internet.

Everybody knows it is unwise to leave computers largely unprotected connected to the internet. However, there are cases in which this is still common practice. For exampe, academic sites with hundreds of users often have a policy of allowing logins from over the world. They are under constant attack by "kiddies" trying to break in to the system by password guessing. pam_shield aims to detect and block these "kiddies".

pam_shield was developed by Walter de Jong in 2006 and 2007.

The author cannot be held responsible for any consequences or harm caused by this software.

Gentle.NET is an RDBMS independent object persistence framework. Gentle.NET features automatic SQL generation and object construction, an SQL factory for creating custom queries, DataView construction helpers, excellent performance and reasonably complete docs.
The framework defines a few attributes with which you have to decorate the objects you wish to persist. Decorate classes with the TableName attribute, and members (properties and fields as you see fit) with the TableColumn attribute.
There are additional attributes available which need only be used when no Analyzer class exists for the database you are using (see Database Provider - Implementation Status). The Analyzer classes are used to obtain metadata on the current schema directly from the database, thus bypassing the need for replicating this information in your code.
If no Analyzer exists, primary key columns must be decorated with the PrimaryKey attribute, and foreign keys and their mappings must be declared using the ForeignKey attribute. The TableColumn attribute provides properties allowing you to provide details on type, size and null-handling. If an Analyzer does exist, the information obtained automatically overrides any such setting.
Business objects may optionally inherit from the Persistent class, which provides a set of standard methods for persisting and retrieving objects. You can replicate these on a different base class if needed, or on a manager class if you prefer a more SOA-oriented design. Gentle provides support for identity columns (where the database assigns a primary key value to the row being inserted) to implementors of IPersistent (which includes the Persistent class).
The main access point into the framework functionality is provided by the PersistenceBroker class, which is responsible for orchestrating all access to a given database provider.
The PersistenceBroker is responsible for basic query construction and caching, as well as interaction with the database backends. You can create as many PersistenceBroker instances as needed, such as one for every database to which you need to connect. Various classes permit or require you to pass a PersistenceBroker instance, which will be used subsequently for all database operations performed by the class.
If you need to connect to a single database only, you can use the static Broker class, which delegates all calls to a default PersistenceBroker instance (using the DefaultProvider configured in the configuration file).
Persistent objects are identified by a Key, which is really just a Hashtable with some convenient methods for gathering property values from objects. The Key class knows how to populate itself when given an object instance and a set of property names, and also provides a means of obtaining a key holding just the primary key fields.
This is useful when constructing custom queries as constraints can be passed as Key instances to methods on both the (Persistence)Broker and SqlBuilder classes. This encapsulation also enables Gentle to work with multi-column primary keys.
To execute custom SQL statements use the SqlStatement class. Use the SqlBuilder class to construct instances of this class whenever the statement is for a supported type (i.e. a class decorated with the proper attributes as outlined above).
The SqlBuilder provides a database independent way of constructing queries and has many methods for adding constraints and otherwise customizing the query. It is used internally by the PersistenceBroker whenever it needs to generate statements.
You can declare a DataView layout using the CustomView attribute on the properties to include in the DataView. The actual DataView can be obtained using the ObjectView class by supplying an array of business objects.
Multiple statements can be transacted (grouped) using the Transaction class.
Enhancements:
- This release features a complete rewrite of the cache subsystem, with significant performance improvements as a result.
- There have also been several minor improvements and bugfixes throughout the code base.