Free to alter software for linux

Proxy Detector is a PHP class that can detect HTTP requests via proxy. This class can detect if a visitor uses a proxy server by scanning the headers returned by the user client.
When the user uses a proxy server, most of the proxy servers alter the header. The header is returned to PHP in the array $_SERVER.
Enhancements:
- This is the first release of the class and implementation example.

TuxFighter is an asteroid-like shooter written in python/pygame.

Your goal is to waste valuable lifetime (or even paid worktime) while steering and spinning a pinguin-shaped alter ego throug a universe full of nasty enemys. The enemys try to collide into you but YOU CAN FIGHT BACK !

Shoot rockets at your enemys but be warned, you have always just twice the number of rockets as the number of enemys on the screen. So aim careful, because some rockets may bounce back from the edge of the screen.

Gain extra points or even applause by killing enemys be a rocket reflecting from walls. Enter the highscore-list and try to improve your shot/miss ratio.

XAO::Web is a part of XAO open source web services suite. It allows to build dynamic web content using data, templates and external input.
The distinguishing feature of XAO::Web is in its modular design where almost every aspect of functionality can be altered and alterations can be re-used. No complex code is embedded in the templates which allows to upgrade code and templates separately or maintain multiple visual representations of the same functionality at the same time.
Installation
perl Makefile.PL
make
make test
sudo make install
Saying "install XAO::Web" from the CPAN shell is a good way too:
perl -MCPAN -eshell
install XAO::Web
Using CPAN shell is usually the best way because all dependencies will be resolved automatically.
If you do manual installation then XAO::Web depends on at least the following modules (look into Makefile.PL or just watch closely the output of `perl Makefile.PL for additional dependencies):
XAO::Base
XAO::FS
Digest::MD5
Error
MIME::Lite
Test::Unit
When you run "perl Makefile.PL" you will be asked for XAO::Web test database. That database is only used when you do `make test and it have to exist. It does not matter what is inside the database, it will be completely wiped out for each test case.
Normally the database should be the same that you have used for XAO::FS tests and in case of MySQL is usually test or test_fs.
The directory where templates get installed is the same that you gave to XAO::Base when you installed it. Normally that directory is /usr/local/xao -- we will assume that for the rest of the document.
Main features:
- Perl code is not mixed with templates. Templates can be normal HTML files if no processing is required.
- A specific site can replace or modify standard XAO::Web objects if required by overriding or extending their methods. You do not need to re-implement entire object to make a site specific change. In case of system object upgrade or bug fix there is no need to alter site-specific changes normally.
- Site can create any extension objects or embed third-party extensions as well.
- One server can serve arbitrary number of XAO::Web sites each with however extended functionality without creating any conflicts. That includes different modifications to the system objects for different sites.
- Not limited to Web environment, allows to build any dynamic content -- content of mail messages or reports for instance.
- Works with CGI or mod_perl (mod_perl is recommended for production grade sites).
- If used in mod_perl mode improves performance by using caching of configuration, parsed templates, database handlers and so on.
- XAO::Web is by default integrated with XAO::FS (see XAO::FS) as a database layer, but this is not a requrement -- if for any reason a different database must be used for a site it can be easily and gracefully achieved.
- Hosting providers can allow their customers to build very complex sites without allowing them to execute arbitrary code, by allowing to modify only templates.
Enhancements:
- Fixed a problem with Web.pm for mod_perl usage, introduced last minute just before releasing 1.06

LiteMan is a simple GUI database manager for the SQLite embeded database engine version 3. It is written in C++ using the Qt toolkit, and is free software under the terms of the GNU GPL license.
LiteMan is meant to be used a quick tool to build database files for dynamic websites and application file formats, but can be used as a generic database application (though a low-level one).
Main features:
- Create and view any SQLite3 database file
- Create, delete and alter new and existing tables
- Create and delete database views
- Run quaries by either direct SQL code or by a dialog
- Export your tables and views to a SQL dump file
Known Issues (and missing features)
- Table field comments are not stored.
- The only way to alter a table is to rename it. Anything other requires re-creating the table.
- There are no means to alter a view.

Sophosticated consists of two BASH scripts. One script installs Sophos virus scanner updates from CD, while the other downloads, unpacks, and installs the latest IDEs.
These scripts needs BASH or a compatible shell. They were originally made and tested on a Mandrake Linux 8.0 installation (and still work fine up to Mandrake 9.1), so you may need to alter the paths to the utility programs (ls gawk grep mail logger eject) to suit your system. I also installed Sweep in /home/sweep rather than the default directory, which you may not have done. The site I made this for doesnt use InterCheck.
I run auto_update_ides thrice daily and auto_update_sweep daily, the clients staff leave any new Sophos CD in the drive over the weekend so that the update script can see and use it. The example crontab reflects this. To use it as-is (and this presumes that you have nothing else in roots crontab, do "crontab -l" to check), do "crontab crontab" in this directory.
The scripts work for me, they will probably work on any reasonably well-equipped Unix system, and maybe many others such as BeOS, OS/2 and OS/X, but as I said above there is no guarantee or warranty of any kind. If you break it, you get to keep both pieces (under the terms of the GPL, of course).
Yes, this even includes Dohl MacBride and his cronies, to whose level of pettiness and selfishness I refuse to stoop.
Enhancements:
- The "top directory" is now explicitly defined at the top of each script. If you install Sophos in /home/sweep as I do, you will need to edit this. The current settings match Sophos default (/usr/local).
- Since /usr/local/tmp normally doesnt exist, the scripts will use $TMPDIR for scribbling if $TOPDIR/tmp doesnt exist.

Bigtop is a web application data language processor.

SYNOPSIS

See Bigtop::Docs::TentTut or Bigtop::Docs::Tutorial for how to create a Bigtop file. Bigtop::Docs::TOC is a guide to all of the documentation modules.
The real synopsis:

vi your_app.bigtop (or use tentmaker see Bigtop::Docs::TentTut)
bigtop --create your_app.bigtop all

Modify your bigtop file and try again:

bigtop docs/your_app.bigtop all

Bigtop is a language for describing the data of a web application. Usually this data will be stored in a relational database. Once you have a description of your data, you can generate a web application from it. This includes all the pieces you need like: the sql statements ready for feeding to your database command line tool, the httpd.conf you need to Include in the httpd.conf on your system, the modules that will handle the web requests, the models that make the database tables look like classes, etc.

If you need to alter the data model in the future, you can change your original description to match the new reality, then regenerate the application without fear of losing hand written code (though you may have to modify some of it to reflect the new reality).

FUNCTIONS

This module is really a place holder, but it does provide some developer routines (which are not exported):

write_file
use Bigtop;
Bigtop::write_file( $file_name, $file_content, $no_overwrite )

This attempts to write $file_content to $file_name and dies on failures of open or close. Further, if you pass a true no_overwrite flag, it will check to see if the file exists and refuse to overwrite it. In that case, the user gets a warning that the file has been skipped because it already exists. If you dont want the user to see the warning, turn off the Bigtop warning. To avoid fatal errors on write failures, wrap in an eval. Putting these together, we come to my typcial usage:

eval {
no warnings qw( Bigtop );
Bigtop::write_file( $some_output_file, $content, no_overwrite );
}
warn $@ if $@;
make_module_path

(Note that make_module_path uses File::Spec, so even though Unix directory syntax is shown below, the function should work in other places.)

use Bigtop;
Bigtop::make_module_path( $build_dir, $module_name );

This attempts to make all the directories from $build_dir to the home of the module. It assumes that lib comes immediately after $build_dir.

For example, a call like:

Bigtop::make_module_path(
/home/username/App-Name, App::Name::Subname
);
Attempts to make these directories:
/home/username/App-Name/lib
/home/username/App-Name/lib/App
/home/username/App-Name/lib/App/Name
/home/username/App-Name/lib/App/Name/Subname

It doesnt report failures. Making directories can fail because the directories already exist (in which case you probably dont care) or because they could not be written (in which case youll notice soon enough, when you try to write to them).

MailManager helps teams deal with large volumes of email by allocating mail to the right person, providing tools to help answer it (prioritisation, reply templates, and a knowledge base), and allowing managers to set service levels for different types of mail and report on performance against service levels and volumes received.
MailManager is based on Zope which is required to use it. MailManager is cross-platform, but most of the testing has been under Linux and Mac OS X.
Whats New in 2.0.10 Stable Release:
- Added in fix for security issue
- Postgres encoding security hole (#1494281)
- The code in the 2.0.9 and previous releases may be vulnerable to this issue, depending on your postgres configuration. The exploit may allow an attacker to alter data in the SQL database and gain access to the web interface as an administrator. You are strongly advised to upgrade.