Free softball socks software for linux

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 )

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.

Secure MTA is a daemon for SMTP passwords and a starter for ssmtp or msmtp.
Options:
smta [-d [-l < numer >] [-t < timer >] [-b]] | [[-e]|[-mta < mta >]] [-sock]
-d | --daemon daemon function
-l | --listen listen number [default: 2]
-t | --timer timer [default: 0=disactivated]
-b | --background background
-e | --exit close a daemon
-s | --socket unix socket [default /home/bakunin/.smta.sock]
-m | --mta msmtp|ssmtp
-h | --help this help
Usage:
smta -d -> starts as daemon, asks the password, and accepts request to unix socket.
smta -m -> connects to smta daemon, gets the password and runs the mta.
Exemple:
set to .muttrc the lines:
set sendmail="/usr/bin/smta -m ssmtp -au bakunin"
---- ~/bin/posta ----
#!/bin/bash
# download new emails:
fetchmail -a
# Set the smtp password:
smta -d -b -t 3600
# Mutt
mutt
# Close the smta
smta -e
mutt runs smta, and smta runs ssmtp -au bakunin -ap password
Enhancements:
- Man page updates and a bugfix for the Unix socket path.

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.

MOCKS is a small, easy configurable, RFC1928 compliant SOCKS 5 server. MOCKS supports upstream proxy and IP-based client filtering rules.
Compiling and Running MOCKS
Due to the simplicity of MOCKS, a make file was uncalled for. You can compile MOCKS with the build script included in this package (build) or with the following command:
gcc -lnsl -o mocks child.c error.c misc.c socksd.c up_proxy.c
If you encounter any problems during compilation dont hesitate to contact me (see section 5 of this file for details).
You can then control MOCKS like this:
Starting server:
./mocks start
Shutting it down:
./mocks shutdown
Get command line help:
./mocks --help
Enhancements:
- Username/Password-based authentication has been added.

VirgoFTP is an FTP GUI based on SWT. VirgoFTP provides a CuteFTP-like interface for users who turn from Microsoft Windows to Linux.
Main features:
- A "true" Universal FTP Client. VirgoFTP can be installed and run on a wide variety of platforms such as Linux ,Mac OS ,Solaris.
- VirgoFTP allows you to work with multiple FTP sites simultaneously. Each session will create a new Tab making it easy to switch between sessions.such like CuteFTP in Microsoft Windows flatform.
- Support RFC959 protocol.
- Proxy/Firewall
- VirgoFTP support SOCKS proxy(version 5),and HTTP proxy, including authentication.
- Transfer:
- Support muliple transfer thread when transfer directories.
- Resuming of interrupted binary transfers supported.
- Passive and active modes are supported (PASV and PORT).
- Support FXP , can auto manager the transfer between two standard FTP Server.

snarf provides a command-line URL retrieval tool with some unique features.
Snarf is a simple utility that is similar to wget, curl, ncftp, lynx, and fetch. Its main advantage is its small size (its ideal for using on a rescue disk). It is also full featured, supporting ftp and http resume, http and ftp authentication, http redirect, proxies, SOCKS, gopher, progress indicators, and it uses configure.
USAGE
If you have an URL (for example, http://foo.bar.com/picture.jpg), you type the following (the $ below represents the command prompt):
$ snarf http://foo.bar.com/picture.jpg
snarf will fetch the file and save it to your local system with the name picture.jpg. If you want to save the file under a different name (for example, background.jpg), you type the following:
$ snarf http://foo.bar.com/picture.jpg background.jpg
snarf saves the file with the name background.jpg. If you want snarf to send the file to standard output, you would type the following:
$ snarf http://foo.bar.com/picture.jpg -
When snarf sees a dash as the local file name, it sends everything it fetches to standard output.
Enhancements:
- Fixes for two longstanding redirect-following bugs, and poor FTP behavior that confused certain servers.
- Users of any copy of snarf > 2.0 can upgrade by running the command "snarf LATEST".