Free allied force software for linux

Star Trek Voyager: Elite Force is a modification to the icculus.org maintained quake3 engine
to make it possible to run EliteForce holomatch. This means: you can *not* play single player missions with this project.
This engine has full compatibility for the newer _and_ the original EliteForce protocol, clients using the original engine can use newer servers, and clients using my engine can use old servers, too.

Now, the next few paragraphs are just some random blabla about the advantages of this release, but if you want to you can just skip it and go right to the installation instructions.

What was the motivation for me doing this project?

It actually started pretty small.. The Quake3 source has been released more than half a year ago and I got the crazy idea to try the quake3 engine with EliteForce on my trusted Gentoo Linux.

When I started the program first the screen went black and nothing happened... nearly nothing. I heard some sounds and when I moved the cursor I heard random click-clicks from the mouse going over some menu buttons. This meant this stuff is not completely incompatible after all, it didnt crash right away though that was exactly what I expected it to do. I digged in Ravens multiplayer source that they released (only the virtual machine stuff, to allow for building modifications) and compared it to quake3s virtual machines and realized that there was a small
incompatibility in one of the data structures used to pass information between engine and virtual machine. It was nothing big and after fixing this the menu worked!

There were some quirks here or there, but most of the menu really worked. So it got me thinking: If I fix all these incompatibilities.. maybe I can finally play my beloved multiplayer game Ive been clinging to for over 5 years on my favorite OS natively.. and IPv6 support for EliteForce would be pretty cool too...

So a crazy idea was turned into a serious project. I had to add support for Ravens models, playing mp3s, EliteForces own network protocol. My goal was to make this release as close to the original as possible. Most of the time, I only could guess what names and functions would mean to the engine or I had to compare the original game and then try to make it work the same way in my engine.

The quake3 game relies heavily on floating point operations. Unfortunately, the original EliteForce engine does non-ISO compliant rounding of floating point numbers to integers in the VMs. The game VM uses that flaw which will result in higher jumping for certain com_maxfps settings. As with the new engine there are many platforms that can be supported, there are probably many different ways one has to take to revert the rounding to the old behaviour. This is nearly impossible to do, so I had to use a different approach: build new VMs.

Test::Differences Perl module contains test strings and data structures and show differences if not ok.

SYNOPSIS

use Test; ## Or use Test::More
use Test::Differences;

eq_or_diff $got, "anbncn", "testing strings";
eq_or_diff @got, [qw( a b c )], "testing arrays";

## Passing options:
eq_or_diff $got, $expected, $name, { context => 300 }; ## options

## Using with DBI-like data structures

use DBI;

... open connection & prepare statement and @expected_... here...

eq_or_diff $sth->fetchall_arrayref, @expected_arrays "testing DBI arrays";
eq_or_diff $sth->fetchall_hashref, @expected_hashes, "testing DBI hashes";

## To force textual or data line numbering (text lines are numbered 1..):
eq_or_diff_text ...;
eq_or_diff_data ...;

ShellTer is an iptables-based firewall. What sets it apart from the rest is that it has built-in SSH brute force protection.
ShellTer project is easy to configure and has an interactive CLI installer.
To install ShellTer, simply execute the "installer" file in this directory.
Enjoy and feel free to email me with questions/comments/patches/etc.
Enhancements:
- Simple bugfix

SQLIer is a script that uses brute force to crack passwords through "true/false" SQL injection vulnerabilities. With "true/false" SQL injection vulnerabilities, you cannot actually query data out of the database, only ask a statement that is returned "true" or "false".
SQLIer takes each characters ASCII code and asks a "higher/lower" question to the database, eventually reaching the actual character code. This script also does not use quotes in the exploit to operate, meaning it will work for a wider range of sites.
An 8 character password (containing any character from decimal ASCII code 1-127) takes approximately 1 minute to crack.
Enhancements:
- This release removes the dependency on the "tempfile" command, which apparently is Debian/Debian-derivative specific.
- It should now work on most GNU/Unix platforms.

Games::Mastermind::Solver::BruteForce is a Master Mind puzzle solver.

SYNOPSIS

# See Games::Mastermind::Solver

Games::Mastermind::Solver::BruteForce uses the classical brute-force algorithm for solving Master Mind puzzles.

METHODS

remaining

$number = $player->remaining;

The number of possible solutions given the knowledge the player has accumulated.

This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.

Rails History Plugin is a Ruby on Rails plugin that stores user actions (i.e. URLs that the user has recently visited).
It avoids storage of POST and AJAX requests, and it provides a manual way to specify which actions not to store.
Installation:
Unpack into the vendor/plugin and that should be it.
Usage:
In your app/controllers/application_controller.rb, add a history line like this:
class ApplicationController < ActionController::Base
history :default => "http://default.url.com/",
:max => 10
end
The history function accepts a hash of options
:default, the default URL to redirect
:max, the maximum locations to remember (five by defaults).
None of the parameters are required. If somebody knows of a better way to obtain the default URL, he is welcomed to tell me how.
You can use the method history_skip in your controller if you want to avoid certain location to be stored in the history. By default, action resulting from a POST, PUT, DELETE request or an Ajax request are not stored in the history.
class FooController < ApplicationController
history_skip :action_to_skip
def action_to_skip
# I will not be stored in the history
end
end
In your actions, you can then use the following methods:
last_location: returns the last visited location, can be used with one numeric argument precising how many locations to go back in the history (1 by default),
peek_last_location: like last_location but dont remove it from the history,
redirect_back: redirect the user to the last location in history, it takes the same arguments as last_location,
store_location(force = false): stores the current location in the history, set force parameter to true to store location even if it would be skipped.
Note that if you want to use the plugin to create a "back" link on a page, you must go back two times. For example, using this controller
class HistoryController < ApplicationController
def foo
end
def bar
end
def back
redirect_back(2)
end
end
Ill try to explain clearly why. Lets say that in your bar view, you create a back link wich links to the back action. Now a user visits foo then bar. What you want is your user being redirected to foo when clicking your "back" link. Now your user hits the link. The controller will call the back action. From its point of view, you are in the back action so going back one time would take you to the bar action.
Enhancements:
- This release fixes a bug where a user variable was stored in a class variable instead of a session one, so a user going back would make another one skip a page in its history.
- The plugin no longer stores PUT and DELETE requests.
- A peek_last_location method was added to look at the history without modifying it, and a "force" parameter was added to the store_location method to force storing of a location even if it would normally be skipped.