Free knee pain software for linux

Universal Module Player or UModPlayer, is a audio module "tool-chain", providing you functions to work with modules like playing, exporting, getting information, and more.
Universal Module Player works in UNIX-like platforms, including Linux, Mac OS X, FreeBSD, Solaris...
It uses the Custom LibModPlug audio library, an improved version of the well-known LibModPlug library, supporting more than 20 formats and giving you high playing quality. It uses LibSDL to handle multiplatform sound support.
Main features:
- You can play the supported formats and seek to any order in the song. You have pause, timer, display, and other standard features.
- You can view the pattern notes while playing.
- You can specify noise reduction, megabass, surround, reverb sound options specifying the grade and the delay of most of the options.
- You can create, save and edit playlists to play a selection of modules.
- You can read and export to a file the song builtin message, the song instrument names and the song sample names.
- Each user of your UNIX box can save all the sound options.
- And much more!
Supported Formats
Supported file formats on both Little Endian (Intel x86, etc.) and Big Endian (PowerPC, SPARC, MIPS, Motorola 68000, etc.) platforms:
Impulse Tracker (IT), Scream Tracker (STM), Scream Tracker 3 (S3M), Extended Modules (XM), Amiga Modules (MOD), OktaMED (MED), Oktalyzer (OKT), Unreal Modules (UMX), Composer 669 (669), DigiBooster Pro Modules (DBM), PolyTracker (PTM), and Farandole (FAR)
Additional file formats supported only on Little Endian platforms (support for Big Endian is on development):
MultiTracker Modules (MTM), AFM, AMS, DMF, DSM, DigiTracker (MDL), MadTracker 2.0 (MT2), PSM, ULT
Exporting Formats
You can export or convert any of the above formats to the following file types:
Impulse Tracker (IT)
WAVE Audio File (WAV)
Audio Interchange File Format (AIFF)
Raw Pulse Code Modulation (PCM)
Enhancements:
- Buffer length fixes.
- Playlist commands were a pain. Now we use the first letter of the command name. Also, pressing ENTER does not quit, the user has to explicitly specify to quit pressing q
- Hopefully fixed AIFF exporting bug.
- New section in the README about LibAo configuration, and some misc. rearrangements.

Nmap Parser is a module that implements a interface to the information contained in an nmap scan. It is implemented by parsing the xml scan data that is generated by nmap.
This will enable anyone who utilizes nmap to quickly create fast and robust security scripts that utilize the powerful port scanning abilities of nmap.
Enhancements:
- Parsing of distance information was added. Ignoring of taskend, taskbegin, and taskprogress information was added.
- Tests for nmap 4.20 were added.
- The license was changed to the MIT-style.
- The "always null" bug for the service->protocol call was fixed.

pretrace is a preload library that allows specified (dynamically linked) applications to always be executed under a debugging environment.

pretrace library allows you to specify the percentage of invocations which will be traced, to help you "keep an eye" on applications without bringing the machine to its knees.

To start using pretrace, add libpretrace.so to your /etc/ld.so.preload.

root# echo /lib/libpretrace.so >> /etc/ld.so.preload

You can now specify applications to trace in /etc/pretrace.conf, the format is one application per line, if you would like to specify a debugger append a colon, then the full path to the debugger and any arguments you would like to pass. If you do not specify a debugger, you get the default, strace, which saves the output to .logfile in the current working directory.

An optional number can be appended in the format %N, eg %50, to specify what percentage of invocations should be traced.

# this is a comment
/full/path/to/application[%percent][:/full/path/to/debugger [arg1 arg2 ...]]

An example pretrace.conf is provided with this distribution.

After modifying pretrace.conf, you should execute ptgenmap to generate a new map file, this is used to quickly parse the configuration file with minimal impact on initialisation time.

libpretrace is designed as a debugging utility for developers and auditors, and should not be used in a production environment.

stephanie is a program for hardening OpenBSD for multiuser environments.

Mmmmm, OpenBSD. Functional, secure, free. With an emphasis on security and integrated cryptography, it carries an excellent reputation for plain old "you-just-cant-hack-this-ness". Not perfect, but nothing is, at least theyre not wearing suits and lying to you.

There are a few roles where i believe OpenBSD fits perfectly. One of these is in multiuser environments, where you have large numbers of possibly malicious users with local access. Here the OpenBSD teams commitment to auditing and fixing code provides a level trust in the environment which is hard to find elsewhere. Also, their efforts to provide integrated cryptography means setting up secure access is easy. So, lets take advantage of the freely available source and tailor it to our specific needs.

Details:

In Phrack 54, route|Mike Schiffman wrote a series of patches for OpenBSD 2.4 for Trusted Path Execution (TPE). Stephanie brings a modified version of these up to speed for OpenBSD 2.8 - 3.0, along with some additional features. A trusted path is one where the parent directory is owned by root and is neither group or other writeable. The TPE works off an internal list of trusted user ids. If a given user tries to execute a file not in a trusted path, and their user id is not in the kernels trusted list, they are denied execution privileges. In real terms, this means they cant download, compile and run krad-sploit.c.

In addition to the TPE, a series of privacy patches came along too. Originally supplied as patches for the individual utilities, these are now implemented through kvm(3), and honour trusted users (ie, trusted users are allowed to see all system information). As a practical example, this means that untrusted users will only be able to see information about processes they own, and the stat tools (netstat, iostat, vmstat, etc) will generally be broken for them. It has been pointed out that by going through trying to kill every possible process id you can find other users processes, but you cant really gain any information on them, so this is not really a great concern.

The original TPE patches had one known way of bypassing the execution restrictions, which was using shell redirection to allow arbitrary interpreted language scripts to be run (perl, sh, etc). This has been fixed up, but could possibly be a big pain in the ass, so please pay attention. When an interpreter is invoked, like most things, it creates a new process group with a job count of one. When a series of commands are connected via the | character on the command line, all the commands belong to the same process group and the job count represents the number of commands eg ps -ax | grep something | awk {print $1} has a job count of three, and the ps, grep and awk processes all belong to the same process group.

The one exception to this is when a user logs in, where we find their shell has its job count set to zero. So how can we use this to prevent shell redirection for a given set of programs? We need to be able to distinguish between ordinary commands and interpreters. At the moment this is done by setting the immutable flag on them. So, in kern_exec(), if we find an untrusted user executing something with the immutable flag set and a job count greater than zero, we flag the process as being potentially dodgy. Then in other system calls we disallow read()ing from fd 0 (stdin) and things like dup2(0, n) if the process has been flagged.

There are two main disadvantages to this. First is the system will need to be brought down to single user mode if the interpreter needs to be patched, and secondly, people will have a hard time suing to an untrusted user. Of course, when a user has shell, they can still type any commands that could otherwise be placed in a shell script, but at the least, this will raise the bar a bit.

Finally, Stephanie brings restricted symbolic links, ala the openwall patches for linux. As time permits, im still working on adding additional features, and will add bits of the openwall stuff i like. The basic goal is to add an extra layer of security without being a monumental pain in the ass to legitimate users, so some things wont be there. I havent added the additional hard link restrictions of the openwall patch, but will do something about this later as time permits.

Installing:

Step by step instructions are presented in the install guide which comes with the source. Read it all first, but its reasonably straight forward. It would be a good idea to read the original article (local copy) if you havent already.

Its distributed under the original two clause BSD license, mess with it all you want, but dont get cranky at me if it breaks something.

You can also read the tpe_adm(8) man page online.

Religion is a Perl module that can generate tracebacks and create and install die() and warn() handlers.

This is a second go at a module to simplify installing die() and warn() handlers, and to make such handlers easier to write and control.

For most people, this just means that if use use Religion; then youll get noticably better error reporting from warn() and die(). This is especially useful if you are using eval().

Religion provides four classes, WarnHandler, DieHandler, WarnPreHandler, and DiePreHandler, that when you construct them return closures that can be stored in variables that in turn get invoked by $SIG{__DIE__} and $SIG{__WARN__}. Note that if Religion is in use, you should not modify $SIG{__DIE__} or $SIG{__WARN__}, unless you are careful about invoking chaining to the old handler.

Religion also provides a TraceBack function, which is used by a DieHandler after you die() to give a better handle on the current scope of your situation, and provide information about where you were, which might influence where you want to go next, either returning back to where you were, or going on to the very last. [Sorry - Ed.]

See below for usage and examples.

USAGE

DieHandler SUB

Invoke like this:

$Die::Handler = new DieHandler sub {
#...
};

where #... contains your handler code. Your handler will receive the following arguments:

$message, $full_message, $level, $eval,
$iline, $ifile, $oline, $ofile, $oscope

$message is the message provided to die(). Note that the default addition of " at FILE line LINE.n" will have been stripped off if it was present. If you want to add such a message back on, feel free to do so with $iline and $ifile.

$full_message) is the message with a scope message added on if there was no newline at the end of $message. Currently, this is not the original message that die() tacked on, but something along the lines of " at line 3 of the eval at line 4 of Foo.pln".

$eval is non-zero if the die() was invoked inside an eval.

The rest of the arguments are explained in the source for Religion::TraceBack. Yes, I need to document these, but not just now, for they are a pain to explain.
Whenever you install a DieHandler, it will automatically store the current value of $Die::Handler so it can chain to it. If you want to install a handler only temporarily, use local().

If your handler returns data using return or by falling off the end, then the items returns will be used to fill back in the argument list, and the next handler in the chain, if any, will be invoked. Dont fall off the end if you dont want to change the error message.

If your handler exits using last, then no further handlers will be invoked, and the program will die immediatly.

If your handler exits using next, then the next handler in the chain will be invoked directly, without giving you a chance to change its arguments as you could if you used return.

If your handler invokes die(), then die() will proceed as if no handlers were installed. If you are inside an eval, then it will exit to the scope enclosing the eval, otherwise it will exit the program.

WarnHandler SUB

Invoke like this:

$Warn::Handler = new WarnHandler sub {
#...
};

For the rest of its explanation, see DieHandler, and subsitute warn() for die(). Note that once the last DieHandler completes (or last is invoked) then execution will return to the code that invoked warn().

DiePreHandler SUB

Invoke like this:

$Die::PreHandler = new DiePreHandler sub {
#...
};

This works identically to $Die::Handler, except that it forms a separate chain that is invoked before the DieHandler chain. Since you can use last to abort all the handlers and die immediately, or change the messages or scope details, this can be useful for modifying data that all future handlers will see, or to dispose of some messages from further handling.

This is even more useful in $Warn::PreHandler, since you can just throw away warnings that you know arent needed.

WarnPreHandler SUB

Invoke like this:

$Warn::PreHandler = new WarnPreHandler sub {
#...
};

This works identically to $Warn::Handler, except that it forms a separate chain that is invoked before the WarnHandler chain. Since you can use last to abort all the handlers and return to the program, or change the messages or scope details, this can be useful for modifying data that all future handlers will see, or to dispose of some messages.

This is very useful, since you can just throw away warnings that you know arent needed.

mop(e) snake is a classic snake game which pits you against all the pain in the world. mop(e)snake project runs on Linux, Windows, and GP2X.
You can try its innovative one-finger control method or stick with a more traditional style of play.
Playing mop(e)snake
Press any key to start, and use the arrow keys to control your snake. Eat the pain.
Alternatively, you can use the good old fashioned O, P, Q, A key layout you remember from your ZX Spectrum days. You can also redefine the keys by modifying the config file in ~/.mopesnake/config. Figuring out the format of that file is left as an exercise for the reader.
Press ESCAPE on the title screen to enter the menu, which allows you to change the skill level (Easy, Medium or Hard) and the game mode (Normal or One-button). Press ESCAPE during the game to pause or quit.
In one-button mode, press any key to start, and any key to turn in the direction in which the arrow is pointing. Its tricky at first, but try to get into the rhythm. Its quite fun.
Enhancements:
- mop(e)snake now continues to run if the sound fails to initialize.
- The ability to turn music and sound effects on and off has been added.