Free volleyball socks software for linux

GPL Arcade Volleyball is an SDL remake of the old dos game Arcade Volleyball for several platforms (currently Linux, Windows, BeOS and Mac OS X are supported).

So far it is playable already, but we are planning on introducing several extra features with respect to the original game, while still preserving its sheer addictiveness! So far we already added:

- themes support
- networking game
- more than 2 players games
- several configuration options

Why AV?

It is fun. Play it for awhile: it is simple, fast, it just catches on. Its silly -- yes -- but try and play it with friends. It takes 5 seconds to figure out how to play, and the funky physics somehow just appeals. You could see it as a party game; say youre throwing a party, youd have that sort of game in the middle of several drinks, projected on a large screen, to have people have fun, engage in tournaments and laugh all through the game. Just as youd have with, say, pong. You wouldnt play Warcraft or Flight Simulator in those situations, or would you. Even for a nerds party were talking about.

tsocks provides transparent network access through a SOCKS version 4 or 5 proxy (usually on a firewall).

SOCKS servers are a form of proxy that are commonly used in firewalled LAN environments to allow access between networks, and often to the Internet. The problem is that most applications dont know how to gain access through SOCKS servers. This means that network based applications that dont understand SOCKS are very limited in networks they can reach. An example of this is simple telnet.

tsocks role is to allow these non SOCKS aware applications (e.g telnet, ssh, ftp etc) to use SOCKS without any modification. It does this by intercepting the calls that applications make to establish network connections and negotating them through a SOCKS server as necessary. If youre on a network firewalled from the internet with a SOCKS server for outside access, telnet cant use this server and thus cant telnet out to the Internet., sou you cannot get out.

tsocks is based on the shared library interceptor concept. Through use of the LD_PRELOAD environment variable or the /etc/ld.so.preload file tsocks is automatically loaded into the process space of every executed program. From there it overrides the normal connect() function by providing its own. Thus when an application calls connect() to establish a TCP connection it instead passes control to tsocks. tsocks determines if the connection needs to be made via a SOCKS server (by checking /etc/tsocks.conf) and negotiates the connection if so (through use of the real connect() function )

usocksd project is a user-mode SOCKS5 daemon.

While the usual "socksd" runs as a system service, perhaps on a firewall machine with no users, this one is intended to be run by users themselves.

There are two situations where this is useful:

1. User has access to a machine with less restricted connectivity than the machine he works on.

2. User is on an insecure network and wants all network traffic to be enrypted using "ssh", and has access to a machine running "sshd" on a more secure network. "usocksd" contains special provisions for this situation.

More information on how to run "usocksd" is in the man page.

Installation: sh ./configure; make; make install.
configure takes additional arguments --enable-debug, --enable-norelax and --with-socks5. configure --help for more info.

This program can itself use SOCKS, although I havent tested that option.

Developed on Linux 2.0, tested also on HPUX 10, AIX 4.1, Solaris 2.6.

EB-lite is the name of the rewrite that is being developed of the instant messaging client Everybuddy. EB-lite carries many major advances on the current codebase, the biggest of which is that the user interface is not contained in the same process as the core. How would you like to use the same messaging client everywhere - on your desktop, your console, your browser, even your mobile phone?
This is all possible because eb-lite allows interfaces written on any platform, in any language - they do not even have to run on the same machine. Any number of user interfaces can also connect to the same core.
Main features:
- Free software, distributed under the GPL.
- Supports the following IM protocols:
- MSN
- AIM (TOC)
- ICQ (TOC)
- Yahoo
- IRC
- Jabber
- Group chat (IRC, MSN, AIM, ICQ)
- Away messages
- Automatic translation (using Babelfish)
- SOCKS and (to a lesser extent) HTTP proxy support
- Modular structure allows different interfaces to share the same engine (and thus share preferences, contact lists, etc).
- Message queuing (including across UI sessions)
- Cross-platform code. The core is written almost entirely in ANSI C, making it easy to port to different operating systems. Although mainly developed on Linux, it will also build on other Unixes (including Mac OS X) and Windows.

JOLIE is an interpreter for a new high level programming language, designed for SOAs (Service Oriented Architecture) orchestration (as, for example, WSBPEL by OASIS).
The whole program is written entirely in Java to ensure cross-platform capabilities, following strictly an object-oriented development method focused on components reusability and virtualization.
Where does JOLIE come from?
JOLIE was born as a project for a thesis in computer science at the University of Bologna, Italy. The project is based upon a theoretical calculus equipped with semantics (named SOCK), developed in the same university.
Why JOLIE?
Service Oriented Architectures (SOA) may be really difficult to orchestrate and they imply a lot of problematics about connectivity, loosely coupling, parallel execution and so on. JOLIE is an attempt to solve all these issues, providing an easy to use language which abstracts from them all.
Enhancements:
- A new heuristic for improving incoming communication handling performance has been introduced.
- Lot of bug fixes and performance improvements in the session execution engine.
- Request-Response operations must now declare their throwable fault names.

FTwall is short for Fast Track traffic Firewall, a P2P traffic filtering script, for Kazaa blocking.
Ftwall-2 is an updated version of the original ftwall-1 software which adds new P2p protocols to the set it can control.
Ftwall-2 is an add-on for linux firewalls that allows the control of "Fast Track" peer-to-peer traffic (such as is used by "Kazaa" and its derivatives), WinMX and others using the OpenNAP protocol.
It is designed to block network traffic from P2P client applications running in the "home" (or "green") network from making access to any peers on the public internet. It is designed primarily for use in networks where the security reigme allows "open access" for outbound connections and "tightly limited" access for inbound ones. Ftwall-2 can be used in networks like this to prevent outbound P2P access from the supported protocols, hence restricting illegal file downloads and uploads.
A Fast track "home network" client that establishes an "outbound" connection is (worryingly) immediately available to accept inbound connections through the established TCP/IP socket - even if the gateway firewall blocks all in-bound connections via "normal" TCP/IP and UDP mechanisms. This is a kind of limited "tunnelling" and gives rise to a number of concerns. Other P2P applications and protocols present similar security challenges. Ftwall solves this (and other) problems for the protocols it understands.
Version 1 of ftwall controlled the Fast Track protocol only (Kazaa et al).
Version 2 of ftwall (the version discussed on this page) adds logic to allow blocking of traffic from WinMX and OpenNap clients using a mechanism based on DNS name wildcards. One simple example is the control of WinMXs native protocol which can be blocked by preventing access to IP addresses resolved from any domain name that ends "winmx.com". OpenNAP is similarly controlled using DNS wildcards to "train" ftwall. See the man page (etc) for these new features by following the links at the bottom of the page.
FTwall-2 runs on Linux-based firewalls using kernel 2.4 (tested with 2.4.20) or later and iptables (test with version 1.2.6). This combination of version numbers is the current set employed by RedHat 8.0 - which is the system on which the software has been developed. The software has also been tested briefly on RedHat 9 and Fedora - but I am awaiting more in-depth news of these and other Linux distributions.
FTwall-2 runs well on the "ipcop" firewall, version 1.3.0 (GPL) with the QUEUE target and string match modules added manually. I believe that it will similarly run on Smoothwall 2 (GPL) although I have not tested this. It will NOT run on Smoothwall 1.0 since this is an "ipchains" based firewall, not an "iptables" one.
FTwall-2 has been tested with the following P2P client applications:
Kazaa 2.1.1, 2.5-beta2, 2.5.1
Kazaa Lite 2.0.2, K++ 2.4.3
iMesh 4.1 build 132, 4.2 build 138
Grokster 1.7
WinMX 3.31
Version restrictions:
- Ftwall requires Linux kernel version 2.4, equipped with "iptables" and the "QUEUE" target. The "ip_string" match module of iptables is desirable, but not required.
- Ftwall works with the "current" version of the Fast track, WinMX and OpenNAP network protocols at the time of writing (July 2004). It is possible that it will need to be re-worked if the protocols are changed in future.
- Ftwall does not block the "SOCKS PROXY" connection option of FastTrack. For a complete lock-down, the firewall must block this style of traffic.

SS5 is a socks server that implements the SOCKS v4 and v5 protocol. As a proxy server, SS5 authenticates, profiles and processes network requests for clients.
Socks Server 5 establishes connections to application hosts for client applications. When the client attempts to access the network, the client connects to the SS5 daemon instead of the application host.
Following authentication, clients request that SS5 perform network activities for the client.
The activities might include:
CONNECT
BIND
UDP ASSOCIATE
The SS5 protocol is independent of application protocols, and can assist with different networking services, including telnet, ftp, finger, whois, gopher, and WWW access.
Enhancements:
- Fix code