Free victim software for linux

Fat Fish is an attractive and funny arcade game.

Are you prepared to meet the most hungry fish of the ocean?... Fat Fish is a game where you take the control of a fish who has a insatiable stomach and must to eat his victims who falls infinitely into the ocean.

The game has 4 different objectives, or rather, 4 short-games where you will entertain trying to complete them. During the game and according to how much you eat, you will start to find out that the fish will lose his agility little by little... here is the part where the toilet that is in the right-bottom of the ocean takes part of the game letting you to "shit" to recover your agility and to continue with your food.

Fat Fish has a simple and funny graphic design, it also has funny music and powerful sound effects that give the game a extra points of fun and adiction.
You will be able to setup your controls, the video mode, sound, music, graphic effects and all the necesary to setup de game according to the needs of your computer or according to your preferences.

This patch can be used on a masquerading firewall (NAT) to keep a log of all the outgoing masqueraded TCP connections.
Its even possible to log the name of the user who has opened the connection. This can be a useful security tool for many small networks that are hidden by a masquerading box if users cannot be totally trusted. It can be used with linux 2.2.17, 2.2.19, 2.2.20 and maybe other (future) 2.2.x versions.
With this information you can know, in the above scenario, that the connection masquerader.yourdomain.com:666 [-3-] ==> crackme.victim.com:31337 [-2-] was started by attacker.yourdomain.com [-1-] from port 1234.
Now please note that this is NOT enough: if attacker.yourdomain.com is a multiuser machine at that time there could be 100 users logged in. Moreover a malicious user could attack crackme.victim.com from attacker.yourdomain.com even without being logged in (with either cron or with a background job or... etc.).
Since we dont want the users being able to hide themselves in this way, the masquerader makes a IDENT query to the client and, if IDENT is available, adds the response to the log together with [-1-], [-2-] and [-3-].
Its therefore recommended (although its optional) that you enable the IDENT service on all hosts on the internal network. Please note that if you restrict the IDENT service (e.g. with TCP wrappers) to the masquerader it wont work (exercise: can you understand why?). If your network configuration on the masquerader is OK, remote hosts wont be able to do IDENT queries (since they cant pass through the masquerader). Therefore allowing "everyone" to do IDENT queries on the clients should be safe enough. If you wish to allow remote hosts to do IDENT queries you can install a special IDENT server on the masquerade router, like pnidentd (for example).
Enhancements:
- Update for linux 2.2.19

Qpsmtpd::Plugin::Quarantine is a filter outbound email to prevent blacklisting.

SYNOPSIS

Qpsmtpd quarantine plugin:

use Qpsmtpd::Plugin::Quarantine;

The quarantine.cgi web page:

use Qpsmtpd::Plugin::Quarantine::CGI;
main();

In crontab or nightly:

perl -MQpsmtpd::Plugin::Quarantine::Batch -e cronjob()

In crontab (every five minutes?):

perl -MQpsmtpd::Plugin::Quarantine::Batch -e sendqueued()

From the command line:

perl -MQpsmtpd::Plugin::Quarantine::Batch -e mailq()

Qpsmtpd::Plugin::Quarantine implements and outbound mail filter. A substantial number of internet sites will blacklist senders if they send too much spam. Most will do this without providing enough feedback for you (the sender) to figure out where the spam is coming from or why you were blacklisted.
I run ISPs and Ive been blacklisted by AOL. Ive been blacklisted by Comcast. Why? Sometimes its because someone is exploting an insecure formmail CGI on my system and sometimes its simply because I allow users to forward email and when they do, they end up forwarding spam.

Qpsmtpd::Plugin::Quarantine understands that sometimes the sender is the victim and sometimes not. The normal situation is that Qpsmtpd::Plugin::Quarantine will bounce things that it thinks are spammy back to the sender with a URL to allow the sender to push the message onwards. However if the particular recipient is on an override list or is very popular (maybe because someone is forwarding their mail to the recipient or maybe theyre on a mailing list) then instead of bouncing to the sender, it will send a note to the recipient letting them know there is a message waiting for them.

Qpsmtpd::Plugin::Quarantine will only send bounces or notifications every so often (configurable). Both senders and recipients have the option (via the website) to have their mail silently discarded so that they dont get bothered again.

Qpsmtpd::Plugin::Quarantine uses OOPS to store its persistent data in mysql or PostgreSQL.

TCFS project is a cryptographic network file system featuring group sharing of encrypted files. TCFS will encrypt your files before sending them to the file server and will decrypt them before they are read by the requesting application.

Because the encryption/decryption process takes place on the client host, no clean data will travel the network. This is particularly valid for the encryption key.

Recent advances in hardware and communication technologies have made possible and cost effective to share a file system among several machines over a local (but possibly also a wide) area network.

One of the most successful and widely used such applications is Suns Network File System (NFS).

NFS is very simple in structure but assumes a very strong trust model: the user trusts the remote file system server (which might be running on a machine in different country) and a network with his/her data. It is easy to see that neither assumption is a very realistic one.

The server (or anybody with superuser privileges) might very well read the data on its local filesytem and it is well known that the Internet or any local area network (e.g, Ethernet) is very easy to tap (see for example, Berkeleys tcpdump application program).
Impersonification of users is also another security drawback of NFS.

In fact, most of the permission checking over NFS are performed in the kernel of the client. In such a context a pirate can temporarely assign to his own workstation the Internet address of victim. Without secure RPC no further authentication procedure is requested. From here on, the pirate can issue NFS requests presenting himself with any (false) uid and therefore accessing for reading and writing any private data on the server, even protected data.

Given the above, a user seeking a certain level of security should take some measures. We propose a new cryptographic file system, which we call TCFS, as a suitable solution to the problem of privacy for distributed file system.

Dynamic Encryption Modules in TCFS:

The dynamic encryption module feature of TCFS allows a user to specify the encryption engine of his/her choiche to be used by TCFS. So you are not forced anymore to use what us (the developer) consider the best (i.e., more secure and efficient) encryption algorithm. The encryption engine must be given in the form of a Linux module and must conform to (the very simple) TCFS API for encryption module. Essentially, it must specify four functions:

1. An initialization function that is called by TCFS when the user pushes her key into TCFS.

Typically the initialization function takes as input the key and returns a pointer to a struct containing a the result of a preprocessing of the key to be used for the encryption and the decryption.

For the specific case of DES the initialization function computes the 16 48-bit subkeys, one for each round of DES.

2. An encryption function which takes a block of data, the length of the block in bytes and the result of the initialization function and encrypts the data.

3. A decryption function which takes a block of data, the length of the block in bytes and the result of the initialization function and decrypts the data.

The encryption and the decryption functions are called each time TCFS needs to read/write a block of data.

4. A cleanup function which performs whatever operation is needed before the key removed by TCFS.

Our work improves on Matt Blazes CFS by providing deeper integration between the encryption service and the file system which results in a complete transparency of use to the user applications.

Release 2.2 of TCFS includes the possibility of threshold sharing files among users. Threshold sharing consists in specifying a minimum number of members (the threshold) that need to be ``active for the files owned by the group to become available.

TCFS enforces the threshold sharing by generating an encryption key for each group and giving each member of the group a share using a Threshold Secret Sharing Scheme. The group encryption key can be reconstructed by any set of at least threshold keys.

A member of the group that intends to become active does so by pushing her/his share of the group key into the kernel. The TCFS module checks if the number of shares available is above the threshold and, if it is so, it attempts to reconstruct the group encryption key. By the properties of the Threshold Secret Sharing Scheme, it is guaranteed that, if enough shares are available, the group encryption key is correctly reconstructed.

Once the group encryption key has been reconstructed, the files owned by the group become accessible. Each time a member decides to become inactive, her share of the group encryption key is removed. The TCFS module checks if the number of shares available has gone under the threshold. In this case, the group encryption key is removed from the TCFS module and files owned by the group become unaccessible.

The current TCFS implementation of the group sharing facility requires each memeber to trust the kernel of the machine that reconstructs the key to actually remove the key once the number of active users goes below the threshold. Future implementations will remove this requirement by performing the reconstruction of the key in a distributed manner.

Sahana project is an integrated set of pluggable, web-based disaster management applications that provide solutions to large-scale humanitarian problems in the aftermath of a disaster.
Main features:
- Missing Person Registry - Helping to reduce trauma by effectively finding missing persons
- Organization Registry - Coordinating and balancing the distribution of relief organizations in the affected areas and connecting relief groups allowing them to operate as one
- Request Management System - Registering and Tracking all incoming requests for support and relief upto fullfilment and helping donors connect to relief requirements
- Camp Registry - Tracking the location and numbers of victims in the various camps and temporary shelters setup all around the affected area.

X-bomber project is a multiplayer game for Unix systems.
"X-Bomber" is multi-player maze-style game where players collect and drop bombs, in an attempt to blow each other up. Last player standing wins!
X-Bomber is vaguely based on "Atomic Bomberman" by InterPlay and "Bomberman" by Hudsonsof. It is played on a grid, rather than with smooth movement.
Main features:
- 4 players on screen, up to 3 may be computer-controlled
- Pairs of players can share the same keyboard (so only two PCs are needed for a 4-human match)
- 2 types of bombs - normal, and remote-controlled
- Randomly-placed boxes with random power-ups inside!
- Occasionally, random boxes of explosive TNT
- 100 level maps!
- A nasty "death" character who appears if the players take too long. He ruthlessly homes in one a character until he catches him... then he picks a new victim!

Search And Rescue project is an air rescue flight simulator. The player pilots rescue helicopters to rescue victims in various situations of distress.

Search and Rescue is a helicopter based air rescue flight simulator. It employs a simple flight dynamics engine that is targetted towards the "average" player. It is not designed to be a cutting-edge realistic simulator, but rather a flexable game that everyone can play and enjoy.

The history of the development of this game goes back to 1997, when Search and Rescue was created as an explorative to design for more complex 3D games using the OpenGL graphics library. Much of the effort in the development of this game came from Wolfpack Entertainment and many dedicated contributors (see credits below).

This game was ported to Windows early on in its development to ensure the portability of its graphics code. However the Win32 version lacked certain features due to differences in Windows design of its graphic, sound, and controller implementation.

The flight dynamics engine (FDE) features helicopter, aircraft, and tilt-rotor aircraft flight dynamics models (FDMs). It uses source-centered (as opposed to world-centered) mathimatical equations to simulate movement which mimicks but does not fundimentally follow standard physics equations. This simplifies the "flyability" of the aircrafts at a slight cost of realisim and lightens processor load.

The 3D visual models of the aircrafts and objects were created by a program called Vertex 3D, an OpenGL modeller designed to create 3D visual models that are optimized for OpenGL.

Each scene is a finite sized flat world, separated vertically by cloud layer(s) and centered at the origin with an artificial longitude and latitude offset applied to displayed positions.