Free openmw 0.6 software for linux

OpenKiosk is an open-source multi-platform kiosk system designed for use in libraries, offices, schools, internet cafes, airports, conference rooms, and more!

Openkiosk aims to be one of the best kiosk software available in the open-souce community. The following prototype screenshots of the OpenKiosk client reflects its evolution towards the goal of acheiving simplicity and elegance in kiosk terminals.

OpenKiosk, is a system made up of a collection of programs that work together in a local network of inter-connected computers. It is a centralized management software for kiosks. It assumes that the resources are shared and centralized as well, including the Internet connection. This implies that the shared Internet connection to the outside world is assumed to be always on at some point within the local network, perhaps a NAT server. It is up to the client program to automatically limit customers individually from accessing the Internet.

When a customer walks in and uses a kiosk or a workstation, the client program obtains his/her login/user account information. It then sends this login information to the server, which in turn, verifies this data and if valid, returns the access rights and duration of use for the customer back to the client program.

The client program at this point, handles the restrictions transparently including preventing running new programs and making it appear that the Internet connection is down if the time limit is reached or if the administrator manually stopped a customer from continuing to use a kiosk/workstation.

OpenKiosk is primarily designed with the multi-user network in mind. From a library containing 20 public browsing terminals to a large internet cafe or convention center containing hundreds to thousands of kiosks or workstations, OpenKiosk is built with components that are designed to scale up. It is not meant to be used on a single stand-alone computer

The Openkiosk system is basically composed of two parts. The first program is called NodeView. It acts as the OpenKiosk central server containing the client information database. It is responsible for administering all the clients on the network either automatically or manually. Monitoring and controlling the workstations can be done locally via the graphical user interfaces or remotely from a Java Applet in a browser.

The second part is simply called "The Client". It is the actual program that sits between the customer and the operating system interface on the workstations. It is the software which physically limits the users access to the Internet, network resources, the local programs on the workstation itself.

For automatic usage, it can take in membership card login. It is also possible to interface to much more advanced hardware readers such as smart card readers. The client is also capable of simple but important tasks such as remote shutdown, instant messaging, file updates and much more.

Presently, there are two versions of clients. The X11 Linux/Unix version, which is an applet that sits on top of the KDE panel (requires at least KDE 3.X) and the Windows version (Windows 95,98,NT,2000,XP).

WmWiFi is a wireless network interface monitor dockapp for the WindowMaker desktop which dislays the signal strength of a wireless card.

WmWiFi is designed to fit well with dockapps like wmnetload and wmcpuload.

JSBlend is a cross-platform, web-based file comparison and merge tool written mostly in Javascript. The tool can display differences in two files and allow the user to selectively merge them by editing one of the files. JSBlend project relies on a Python or PHP backend to load the initial differences between the two files and to save them after merging.

The backend relies mostly on the GNU DiffUtils toolset which is available on Linux and Windows as open-source software. Specifically, the tool uses diff command to load the differences in a side-by-side format (-y option) initially. After this point, all the user edits are managed within the Javascript and no calls to the backend server is made except for saving the files.

While JSBlend is a general purpose diff/merge tool, it is especially suitable for managing conflicts in configuration files on servers after an update. Many server machines do not have any GUI framework installed and are often run in headless mode on remote sites. Using desktop-based GUI tools for merging the conflicts is not always possible. JSBlend can be a very useful tool when either used standalone or embedded inside an existing administration console.

phpMyID is a small, fairly lightweight, standalone, single-user Identity Provider for OpenID authentication.
OpenID is an open, decentralized, free framework for user-centric digital identity (I stole that from their website). But what does it mean? Well, basically OpenID is a way to authenticate yourself to various places (websites) by verifying your identity as the owner of a particular URL (say, a website of your own).
Instead of giving a username and password to a login form, you just give it your URL. Youre then directed to your "identity provider" to log in, and when it authenticates you, you go back to the site you were orignally trying to get into. Why this is good or bad, and what the actual implications of it are... well, thats all mostly outta scope as far as phpMyID is concerned. Suffice it to say, phpMyID acts as an "identity provider" so you can log in to OpenID enabled sites.
From a user point of view, OpenID is a neat concept, but it has a few flaws. For example, when I wanted to actually, yknow, get an OpenID thingie of my own so I could log into OpenID sites, I found there was no satisfactory way to get one. My options were:
Download a ready made application to handle serving up identities and create myself an account in it. - There arent many of these, and what few there are seem to be geared towards multi-user setups. Since theres only one of me, this option seemed like overkill.
Download a complex set of libraries and build an application to handle serving up my identity. - Again there are not many of these, and what few there are seem a bit overcomplicated for my needs.
Set up an account with a third party provider. - A bad option for me because I really dont like the idea of coupling a theoretically decentralized framework to one of a handfull of third party providers (and giving them my account credentials). Sure, someone who doesnt have their own site and server technology will probably go this way, but not me.
Since I couldnt find the simple solution that I wanted, I did what any [idiot|geek] would do, and created the missing option for myself: a single user OpenID server. phpMyID.
Usage
phpMyID is a single user (though, if you were so inclined, you could easily turn it into a multi-user setup) IdP, or "Identity Provider" for the OpenID framework. Its a single PHP script with minimal dependancies.
You dont need a database, you dont need to make your filesystem writable, you dont need to download any libraries, and you dont need to recompile PHP. Okay, well, you shouldnt need to do any of that.
Installing phpMyID requires an MD5 hashing utility. Why? Because you have to authenticate to it using a password. phpMyID uses HTTP Digest authentication for security and your password must be encrypted when you enter it during installation. Say it with me: "passwords should never be stored or transmitted in plain text" (one of the advantages of phpMyID and OpenID is that they never are).
For Linux or OSX (or any other Unix-like OS), I suggest using OpenSSL to encrypt your password. For Windows, there are a number of utilities available, but I recommend this one by Colin Plumb. Its public domain code, and it will do exactly what you need (yes, the hash it create is all upper-case - dont worry, phpMyID will convert it for you). You can use PHPs md5 function to generate your hash for you on the fly, but I must discourage doing so. Not only does it take all the fun out, but you have to store your password in plain text to make it go.
Complete installation instructions, including examples of how to encrypt your password, are available in the provided README file (heres the svn version).
Enhancements:
- This release should fix the outstanding (known) "bad signature" errors, adds a number of refinements, includes a testing mode, and provides support for a more versatile set of "big math" functions.

sgwi is a web-interface to SQLGrey (SQLGrey is a greylister for Postfix).
This web-interface enables you to edit the white- and blacklists as well as the current state of the greylist.
Installation:
- put the files somewhere in your website
- make sure you shield things with a .htaccess file
- edit config.inc.php
Enhancements:
- Certain e-mail addresses could not be deleted.

PIMPPA is a tool to loot binaries from newsgroups (and ftp sites, but the ftp support is probably deprecated). PIMPPA tries to achieve complete "hands free" -operation where possible.
The system is best suited for the Connoisseur, the Collector and the Worshipper of the Mighty Crond. Its not very useful for the minions of the trendy interactive.
Main features:
- Attempts to skip duplicates and spam before downloading actual messages.
- Further duplicate discarding based on filenames & MD5 -checksums.
- Allows user-definable, content-based pruning scripts for even more involved discarding.
- Intelligent multipart handling, downloads only complete postings.
- Supports multiple newsservers.
- Filename-based sorting of accepted files to proper directories.
- Can be used to hunt known file series, extensions or message subject patterns and skip the rest.
- Supports automatic file integrity testing and transformation.
- Several tools and scripts for file maintenance and viewing.
- Knowledge is kept in SQL database, making it relatively easy for you to write your own custom scripts and utilities.
- Cronable: come back next week to check the filtered catch.
- Optional Gnome GUI.
- Its free! - GPLed Open Source.

xSite project is an HTML album generator.
Main features:
- Handles the whole publishing workflow from images to HTML - youre expected to use something else (like digikam) to organize, tag, manage etc. your photos
- Pure, standards-compliant, static xHTML without Javascript or tables
- All image comments are extracted from the actual images (no funny separate text or XML files)
- Efficient method for refreshing albums (subsequent runs only update images where needed)
- Minimalistic requirements: only exiv2 and ImageMagick are required (no MySql, no PHP, no X server even)
Installation and usage:
- Get the scripts: xsite-0.1.tar.gz
- Install the requirements mentioned above (present in most Linux distributions)
- Untar the scripts, read the README and edit xsite for generic changes (album author field etc.)
- Run it as xsite outputdir ~/tmp/MyPictures. The outputdir directory, a new subdirectory called MyPictures within, assorted thumbnails and HTML files will be created for you.
- Check out outputdir/index.html from any browser. Enjoy!
Enhancements:
- Bugfixes to the new RSS generation code.
- The ability to sort RSS feeds by image modification time.
- Minor cleanups.