Free pomstrap 1.0.7 software for linux

POMStrap is a little opensource (BSD License) application bootstrap designed to avoid the Java library dependency/version headache. The more we use open-source Java components, the more we have to deal with the classical problem of dependency conflict.
Ive personally experienced this problem when using FOP and Batik simultaneously: FOP required a specific old version of Batik to work (and render vector images), and I needed to use the latest version of Batik for image rendering.
POMStrap allows you clean separation of concern within your application (for component oriented architecture), providing strict hierarchical classloader confinement.
POMStrap is able to load application dependency as they are declared in Maven 2 project file, and execute each dependency in its own classloader without inhering from its parent avoiding version conflict.
By using POMStrap you will be able to have an application dependency schema such as:
Application-1.0
+ DepA-1.0
+ DepB-1.0
+ DepA-2.0
And DepB-1.0 executing DepA-2.0 classes (and not DepA-1.0 as it would be without POMStrap).
POMStrap also work as an application bootstrap. POMStrap project just requires a pom file (Maven 2 project file) and a class/method to fetch all required dependencies and launch the application using a command line syntax such as:
java -jar pomstrap-1.0.jar groupId:artifact:version classname[:method] [method args]
for example:
java -jar pomstrap-1.0.jar pomstrap:testApp:1.0 com.prefetch.pomstrap.App:run
If no method is provided it will try to start the classical java static main method.
Be default POMStrap looks into you local repository (in you [home directory]/.m2/repository) but you can also specify another repository URL using system property:
"-Dmaven2.repository.url=[URL]"
You can use POMStrap via a Servlet with similar init-parameters configuration (see provided example sources).
A JBoss POMStrap Service is also available and allows you to lauch applications as JBoss Service (via .sar file deployed in a JBoss instance).
By the way, POMStrap can easily be embedded in your application with minimal impact (since it does not require any external library).
Enhancements:
- This release fixes a bug in the resource loader and remote repository definition.
- POMStrap has now been successfully used in a different production environment and this release can be considered as gold.

muhttpd (mu HTTP deamon) is a simple but complete Web server written in portable ANSI C. It supports static pages, CGI scripts, and MIME type based handlers.
It drops privileges before accepting any connections, and can log received requests.
It has been tested on OpenBSD, GNU/Linux, NetBSD, FreeBSD, Mac OS X, and Cygwin. muhttpd runs successfully on 32-bits, 64-bit, little endian, and big endian systems.
muhttpd understands a few configuration directives, described below.
port n Listen for connections on port n
webdir path Use path as the directory containing the web pages
webroot path chroot(2) to path
type type ext+ Treat files whose names end in one of the strings in ext+ (a space separated list) as if they were of type type
handler type program Pass files of type type through program
include file Read file as a configuration file
index name+ Specify which file to send when a directory index is requested. The first matching name is used
user username Switch to username before starting to accept connections
group groupname Switch to groupname before starting to accept connections
logfile file Log incoming requestst to file
Example:
port 80
webdir /var/www
logfile /var/log/muhttpd/logfile
user www
group www
index index.html index.php
type text/html .html
type text/css .css
type text/plain .txt
type application/x-httpd-php .php
type image/png .png
type image/jpeg .jpg .jpeg
handler application/x-httpd-php /usr/lib/cgi-bin/php
Enhancements:
- Fixes logging of IP addresses on OpenBSD.
- Flushes the log file before calling exec(2) to make sure entries make it to the log file.
- Connects standard error to the log file so errors from scripts are logged.

QuFTP is a command line ftp client for Linux. It supports the selection of multiple files for upload and download, which are transfered with one command. I wrote this client out of because i didnt saw any reasonable FTP client for linux.
I can almost guarantee that there are bugs in this thing, but it seems to be reasonably stable here, and I can use it for my day-to-day FTP needs. If you find any bugs, or have any comments, please let me know at david@dparrish.com.
COMPILING:
make
INSTALLING:
make install
cp example.quftprc ~/.quftprc
USING:
quftp -h
type "help" to get a list of commands in the program
Feel free to modify the .quftprc file to your liking, there are
instructions included in the file.
Should be sufficiently easy. You must have the GNU readline 4.0 libraries
installed with the headers in /usr/include/readline. (Thats the place
for it in Red Hat). If you are getting segfaults logging in, its probably
because you have an older version of readline installed. This is something
I would love to fix.
I dont plan on porting to Windows because its not worth it.. there
are plenty of good FTP clients for Windows 95, such as Bulletproof FTP
(http://www.bpftp.com/). I dont have access to any *NIX systems other
than Linux, but if you want to port it to anything else, go ahead,
just let me know, preferably with patches.
Script files can be created as just plain text files. These can contain
any valid quftp command, which will be run one after the other. Run the
script with the -s parameter or the run command. If any command fails,
script processing will cancel, unless the -i (ignore errors) parameter
is specified.
The .quftprc file is just a script file that is always run on startup.
Main features:
- Select an unlimited number of files for upload or download
- Full scripting ability
- Command Line Completion
- Work with multiple FTP servers simultaneously
- Transfer files directly between servers
- Transfer any size files of any type
Enhancements:
- Can transfer files with spaces (Bug 204270)
- Dont segfault on responses without response code (like MOTD)

Timer_q is a shared C library which implements multiple queues of timed events. This is commonly needed, but often implemented badly (via. alarm()).
Timer_q also aims to be small, fast and easy to use.
Enhancements:
- Many fixes were made for corner cases.
- A debug build was added for the development of code using the library.
- A unit test framework and some unit tests were included.

sign is a file signing and signature verification utility. Its main purpose is to be a simple and convenient extension to a tar/gz/bzip2 line of tools to check file integrity and authenticity. Its small and simple, it does just one thing and hopefully does it well.

I needed a tool to digitally sign a bunch of .tar.gz and to allow recepients of the files to easily check, unzip, untar and start enjoying the content as quickly and painlessly as possible.

There are OpenSSL, GnuPG, PGP and others and they are of course perfectly capable of file signing. OpenSSL is probably the most widely spread one and best suited for the role of being a universal signing utility. However the state of affairs is such that OpenSSL as an application is not really used for anything more than generating tarball MD5 hashes. The other packages are plain big and complex for a simple task of file integrity checking. Its like getting a professional sound editing suite instead of a dead-simple .mp3 player. The larger crypto-packages also tend to lack modularity in a sense that to get file signing working I would need to configure a handful of core, but otherwise unrelated settings first. Besides if I am not going to use anything but a signing code, the rest will be sitting there collecting dust, creating untrivial shared libraries dependencies and a general feeling of a wasted disk space.

First of all, sign is a file processing tool, it reads from the files (including stdin) and writes to the files (including stdout). It can be used to attach signatures to the files or to verify and/or strip them.

Between signing and verifying latter will account for a bulk of usage. When checking the signature, sign will check for both integrity and authenticity of the file. An integrity check is done by validating SHA-1 hash embedded into the signature, and an authenticity is ensured by checking signers credentials against a trusted list.

sign adopts OpenSSH-style authentication model, where the trust hierarchy is flat (no certificates), an authentication is done with public keys and the list of trusted keys is grown gradually on as-needed basis.

Every trusted key is associated with a file name prefix called the title. The key can be trusted for signing files, whose name start with keys title. The same key may be associated with more than one title, but not vice versa.

The signature is appended at the end of the file and it carries three bits of information - the title, the public key of the signer and the hash of all preceeding data encrypted with signers private key. The verification is performed as follows:

The filename is checked to start with a title
The hash is decrypted using the public key
The hash is compared to the locally computed value (this ensures integrity)
The title is looked up locally; if its known and associated public key is the same as in the signature, the file is deemed authentic.
Otherwise if the title is known, but the key is different, the file is considered to be signed by untrusted, impersonating party and the check fails.
And lastly, if the title is unknown, the authenticity of the file cannot be established. The user is provided with public key fingerprint, which should be manually authenticated. Then the title and the key are added to the trusted list; and subsequent signatures from the this signer for this particular title will be cleared automatically.

In order to sign files, the signing keypair must first be generated. The keypair is maintained on per-user basis and can be created by running sign with a special command-line flag. The signing process itself is as follows (give or take insignificant details):

Run the filename through a list of owned titles and find the best match. Alternately accept explicit title from the user using one of the command-line flags.
Attach the title, attach public signing key
Compute the hash, encrypt it with private signing key
Attach encrypted hash.

For details on command-line syntax and other operating parameters, please refer to a man page; an online version is here.

LMarbles is an Atomix clone with a slight change in concept. Instead of assembling molecules you create figures out of marbles. Nevertheless, the basic game play is the same: If a marble starts to move it will not stop until it hits a wall or another marble.

To make it more interesting there are obstacles like one-way streets, crumbling walls and portals.

As Marbles is meant as a puzzle game you play against a move limit and not a time limit. This way you have as much time as you need to think.

Libsocketcpp provides a easy-to-use C++ socket library class.
Dispite the name, the TCPSocket class can handle both UDP and TCP connections.
Unfortunatly right now, the class is simple. It does not do anything really fancy like non-blocking sockets, select which interfaces you want to use, etc...
What it does allow you to do is to set up a TCP or UDP server/client and send and receive blocks of data. Plain and simple
Enhancements:
- Fixed missing include inside tcpservertest test program.
- Should be able to compile on RH 7.0 now.