Free socks that rock software for linux

Socks via HTTP provides a socks tunnel via HTTP.

Socks via HTTP is a program converting SOCKS requests into HTTP requests and tunnelling them through HTTP proxies if needed.

The SOCKS protocol allows programs to traverse firewalls on any port number and is used by many popular programs, like Napster, MSN Messenger, CRT(telnet client) and many others.

Many companies restrict firewall traversals only to HTTP requests, disabling SOCKS proxy.

Socks via HTTP provides a miniature SOCKS server for the SOCKS client, performing its connection through an HTTP proxy to a remote server, which establishes the real connection.

Socks via HTTP is 100% Java, and can run on any OS. It is entirely written in Java.

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.

Thinking Rock project is a Java based software application for collecting and processing your thoughts, following the GTD methodology.
Thinking Rock allows you to collect your thoughts and process them into actions, projects, information or future possibilities. Actions can be done by you, delegated to someone else or scheduled for a particular date. Projects can be organised with ordered actions and sub-projects. You can review all of your actions, projects and other information quickly and easily to see what you need to do or to choose what you want to do at a particular time.
Main features:
- It will help you to store in one safe place all the things you have to do or would like to do one day;
- Unlike many task management applications, Thinking Rock lets you to group your actions in projects and sub-projects;
- It gets you moving on your thoughts by encouraging you to think of the next physical action to take;
- It is simple, easy (help documentation provided) and quick to use ;
- We provide free customer support;
- The data file is separate so you can have the application installed on your home computer and at work, and transfer the small data file between computers;
- It is multi-platform: use it on Linux, Machintosh, or Windows;
- Its free.

SOLtalk is an encrypted chat program with proxy support. It has varius frontends which include gtk and ncurses. This program is a client/server encrypted chat program with no features (yet!). For encryption we use twofish and blowfish algorithms.This version supports socks version 4 and 5 (user/pass authentication only works with version 5).

To build run: ./configure
To make run: make
To install run: make install

As simple as that.

Rocks Cluster is a complete "cluster on a CD" solution for x86 and IA64 Red Hat Linux COTS clusters.
Building a Rocks cluster does not require any experience in clustering, yet a cluster architect will find a flexible and programmatic way to redesign the entire software stack just below the surface (appropriately hidden from the majority of users).
Although Rocks includes the tools expected from any clustering software stack (PBS, Maui, GM support, Ganglia, etc), it is unique in its simplicity of installation.
From a hardware component and raw processing power perspective, commodity clusters are phenomenal price/performance compute engines. However, if a scalable ``cluster management strategy is not adopted, the favorable economics of clusters are offset by the additional on-going personnel costs involved to ``care and feed for the machine. The complexity of cluster management (e.g., determining if all nodes have a consistent set of software) often overwhelms part-time cluster administrators, who are usually domain application scientists. When this occurs, machine state is forced to either of two extremes: the cluster is not stable due to configuration problems, or software becomes stale, security holes abound, and known software bugs remain unpatched.
While earlier clustering toolkits expend a great deal of effort (i.e., software) to compare configurations of nodes, Rocks makes complete Operating System (OS) installation on a node the basic management tool. With attention to complete automation of this process, it becomes faster to reinstall all nodes to a known configuration than it is to determine if nodes were out of synchronization in the first place. Unlike a users desktop, the OS on a cluster node is considered to be soft state that can be changed and/or updated rapidly.
This is clearly more heavywieght than the philosophy of configuration management tools [Cfengine] that perform exhaustive examination and parity checking of an installed OS. At first glance, it seems wrong to reinstall the OS when a configuration parameter needs to be changed. Indeed, for a single node this might seem too severe. However, this approach scales exceptionally well, making it a preferred mode for even a modest-sized cluster. Because the OS can be installed from scratch in a short period of time, different (and perhaps incompatible) application-specific configurations can easily be installed on nodes. In addition, this structure insures any upgrade will not interfere with actively running jobs.
One of the key ingredients of Rocks is a robust mechanism to produce customized distributions (with security patches pre-applied) that define the complete set of software for a particular node. A cluster may require several node types including compute nodes, frontend nodes file servers, and monitoring nodes. Each of these roles requires a specialized software set. Within a distribution, different node types are defined with a machine specific Red Hat Kickstart file, made from a Rocks Kickstart Graph.
A Kickstart file is a text-based description of all the software packages and software configuration to be deployed on a node. The Rocks Kickstart Graph is an XML-based tree structure used to define RedHat Kickstart files. By using a graph, Rocks can efficiently define node types without duplicating shared components. Similiar to mammalian species sharing 80% of their genes, Rocks node types share much of their software set. The Rocks Kickstart Graph easily defines the differences between node types without duplicating the description of their similarities. See the Bibliography section for papers that describe the design of this structure in more depth.
By leveraging this installation technology, we can abstract out many of the hardware differences and allow the Kickstart process to autodetect the correct hardware modules to load (e.g., disk subsystem type: SCSI, IDE, integrated RAID adapter; Ethernet interfaces; and high-speed network interfaces). Further, we benefit from the robust and rich support that commercial Linux distributions must have to be viable in todays rapidly advancing marketplace.
Wherever possible, Rocks uses automatic methods to determine configuration differences. Yet, because clusters are unified machines, there are a few services that require ``global knowledge of the machine -- e.g., a listing of all compute nodes for the hosts database and queuing system. Rocks uses an SQL database to store the definitions of these global configurations and then generates database reports to create service-specific configuration files (e.g., DHCP configuration file, /etc/hosts, and PBS nodes file).
Enhancements:
- Rocks v4.3 is released for i386 and x86_64 CPU architectures. New features: Rocks command line - initial release of the Rocks command line which facilitates non-SQL administrative access to the database; PXE First - hosts can now be configured in BIOS with a boot order of CD, PXE, hard disk. Enhancements: based on CentOS 4.5 and all updates as of July 4, 2007; Anaconda installer updated to 10.1.1.63; performance improvement when building torrent files for the Avalanche Installer; database indirects, more flexibility with Rocks variables; Globus updated to gt4.0.4 with web services....

ID3 mass tagger is a portable command-line mass tagger for audio files.
ID3 mass tagger is designed for non-interactively adding, updating or removing meta-information in a number of files with a single command.
It can generate tag fields from the filename and rename files using an intuitive syntax. It currently supports ID3 (1.1) and ID3v2 (2.0, 3.0) tags.
Exemple:
Here are some examples of using id3:
id3 -a "Stallman" -t "Free Software Song" fs_song.mp3"
Add a simple tag to a file.
id3 -d *.mp3
Removes all ID3v1 tags from all mp3s
id3 -g "psych rock" *.mp3
Sets genre to "Psychedelic Rock" all mp3s
id3 -2 -1 -u "*.mp3"
Copy ID3v2 tag to ID3v1 tag in all files.
id3 -a "TAFKAT" -n "%1" -t "%+2" "*. *.mp3"
Update tag fields similar to this;
id3 -a "TAFKAT" -n "01" -t "My Song" "01. my_song.mp3"
id3 -a "TAFKAT" -n "02" -t "Untitled" "02. untitled.mp3"
id3 -2 -f "%a - %t.mp3" blaet.mp3
Rename file to a standard "Artist - Title" format, using ID3v2 values.
id3 -g "alt rock" -a "The Author" -l %1 -n %2 -t %3 "Author - */(*) *.mp3"
Process multiple directories at once.
id3 -g "alt rock" -a "The Author" -m "Author - %l/(%n) %t.mp3"
Shorthand for the previous example.
id3 -a %t -t %a "*.mp3"
Swap artist and title fields in all mp3s.
id3 -D source.mp3 -1 -2 dest.mp3
Copy ID3v1 and ID3v2 tags of source.mp3 to dest.mp3
id3 -D source.mp3 -1u -2u dest.mp3
As above, but only replaces the non-standard or blank fields in dest.mp3 by data from source.mp3.
id3 -2 -rAPIC -s 0 *.mp3
Removes embedded images and padding from all mp3s.
id3 -2 -rAPIC -s 0 -R "*.mp3" "/my documents"
As above, but works recursively on all mp3s in the directory tree starting at /my documents
id3 -2 -q "%| %a - %|Untitled|t || %t || %1 |?" "*.mp3"
Generate a playlist, using the best possible text
id3 -2 -c "Was: %_f" -f "%a - %|Untitled (%#x)|t.mp3" "*.mp3"
Advanced rename. Saves previous filename in the comment field, and renames files without proper tags to;
Unknown - Untitled (01).mp3
Unknown - Untitled (02).mp3
... etc
Enhancements:
- This release adds support for Lyrics3 tags.

Linux Audio Backstop project is a system for automated scheduling of audio recording and playback in a broadcast environment.
It includes features for controlling external audio switcher devices by means of serial and TCP/IP commands, as well as the ability to record and playback relay closures by means of the line of digital GPIO cards manufactured by MeasurementComputing.
The Linux Audio Backstop runs on the popular GNU/Linux operating system. It is freely available under the GNU General Public License.
Main features:
- Record and Playback up to four feeds simultaneously.
- Programmable from any web browser.
- Supports capture and playout of up to twenty-four discrete relay closures.
- Very lightweight and efficient - a Pentium 1 system is capable of hosting a complete system
- Runs on the rock-solid GNU/Linux operating system.
- Totally free and open -- No dongles, unlock codes, software keys or other arbitrary limitations.

ProxyTools is a package of Perl network utilities designed mainly to assist those whose Internet access is censored, unreliable, or otherwise damaged. Uncensored access is provided to any outside service required (Usenet News, Web browsing, IRC, Socks etc.). Setup requires installation of Perl and some modules; this is doable by even a novice MS Windows user with email instruction, allowing help to be provided to those inside these countries from expert users outside.

In pursuit of this rather non-specific goal, some interesting network utilities are already produced. We think the code is interesting in itself, useful in other areas, and would welcome contributions to the overall sum of ideas, concepts and ideals expressed in these tools.

The project is of interest to the following groups of people:

those who live in Internet censoring countries (or corporations, schools, universities) such as the Middle East (United Arab Emirates, Kingdom of Saudi Arabia, Kuwait, Syria), China, Burma, etc.
those who would wish to assist those in the group above.
those who are interested in Perl code dealing with many aspects of networks at the socket level, and transactions using HTTP proxies. One tool in this project offers a failover capability, and intelligent choice, between various censor-bypassing strategies and network paths, offering the user a robust, uncensored connection even in a low bandwidth, unreliable, packet filtered and proxy-poor environment.
those who administer the firewalls which do the censoring, and those who might be considering this.
those who are just curious about the current techniques used by the first group above.