Ports Search

WebAuth is an authentication system for web pages and web applications. The first time a user attempts to access a web page protected by WebAuth, they will be sent to a central login server (weblogin.stanford.edu at Stanford) and prompted to authenticate. Normally, they will be asked for a username and password, although other authentication methods are possible. Once the user has logged in, the weblogin server will send their encrypted identity back to the original web page they were trying to access. Their identity will also be stored in a cookie set by the weblogin server and they will not need to authenticate again until their credentials expire, even if they visit multiple protected web sites. WebAuth works with any browser that supports cookies, requires no agents or other software installed on the client web browser systems, and works with an existing Kerberos v5 authentication realm. It can also be used as the SSO provider for a Shibboleth IdP and supports SPNEGO authentication as well as username/password over TLS/SSL. See the page on WebAuth features for more major features and a brief comparison with other web authentication systems.

This is a port of G-Cows, a software project consisting in: - definition of a scripting language designed for creation of web sites (Cows); - interpreter for the scripting language (cows); - a makefile generator (cows-mkgen). Cows is a scripting language whose main goal is to make the creation and updating of a web site faster, more flexible and less prone to errors without relying on server-side technologies. Cows allows to use your Unix background and your favorite tools while creating a site: you can traverse the whole directory tree with `find', extract informations with `grep', build complex pipelines, include external scripts and programs written in every language whose interpreter or compiler is installed on your system. Even if you use server side technology, you can still appreciate Cows for every task not relying on dynamic change of your site's contents mixing Cows, PHP, custom Apache modules, application servers etc. Cows gives the best results when used in conjunction with the Make utility, available on all Unix systems.

Parse::HTTP::UserAgent implements a rules-based parser and tries to identify MSIE, FireFox, Opera, Safari & Chrome first. It then tries to identify Mozilla, Netscape, Robots and the rest will be tried with a generic parser. There is also a structure dumper, useful for debugging. User agent strings are a complete mess since there is no standard format for them. They can be in various formats and can include more or less information depending on the vendor's (or the user's) choice. Also, it is not dependable since it is some arbitrary identification string. Any user agent can fake another. So, why deal with such a useless mess? You may want to see the choice of your visitors and can get some reliable data (even if some are fake) and generate some nice charts out of them or just want to send an HttpOnly cookie if the user agent seems to support it (and send a normal one if this is not the case). However, browser sniffing for client-side coding is considered a bad habit.

From the website: What is PHP Surveyor? PHP Surveyor is a set of PHP scripts that interact with MySQL to develop surveys, publish surveys and collect responses to surveys. Once a survey has been created it can be published as an online survey (displayed as single questions, group by group or all in one page) or you can use a dataentry system for administration of paper-based versions of the survey. PHP Surveyor can produced 'branching' surveys (set conditions on whether individual questions will display), can vary the look and feel of your survey through a templating system, and can provide basic statistical analysis of your survey results. PHP Surveyor includes the capacity to generate individualised 'tokens', so if you have a list of people you want to invite to participate in a survey you can issue each one with a token, and they will be able to access the survey using that token. This allows for quite good quality control of your surveys.

"twander" is a Filesystem Browser which runs on both Unix-like systems as well as Win32 systems. It embraces the best ideas of both similar GUI-driven programs (Konqueror, Windows Explorer) as well as text-based interfaces (Midnight Commander, List, Sweep). While the "twander" interface is graphical, all the major navigation, selection, and execution commands can be entered from the keyboard, not just the mouse. This means Power Users who are strong typists can minimize dependency on the mouse and materially speed up their interactions with the system. Moreover, unlike the other programs, "twander" does not have a built-in set of commands (which typically cannot be changed). Instead, "twander" supports a rich macro configuration language for virtually limitless user-definition of commands. The configuration language provides a simple mechanism for communicating the list of items currently selected in the GUI to the user-defined commands. Each user is thus free to configure a command set unique and appropriate to their needs. As with the navigation commands, user-defined commands can be invoked with either the keyboard (a single keystroke) or the mouse (a menu selection).

This utility notably decreases the startup time of your X sessions, provided that you start a number of X clients automatically during the X session startup. Most people, for instance, start X clients like xterm, xclock, xconsole and xosview from their .xinitrc, .openwin-init, .xtoolplaces or .xsession file. These X clients are started simultaneously (in the background) which puts a high load on the X server and the OS: * The X server is not multi-threaded, so all X clients are competing to get access to the X server and to use its resources, which causes a lot of overhead (= delay). * The performance of other (non X related) tasks served by the system degrades badly due to the high load. If the system has not enough RAM to hold all the X clients, it is swapping heavily, resulting again in a lot of delay. On the Sun platform there is a utility called 'toolwait' which solves these problems: it starts one X client in the background, waits until it has mapped a window and then exits. Xtoolwait is a free implementation of exactly the same idea.

Fastjar is a version of Sun's `jar' utility, written entirely in C, and therefore quite a bit faster. Fastjar can be up to 100x faster than the stock `jar' program running without a JIT. Currently, the author is working on adding all the features present in the Sun utility. At the moment, implemented features are: * Archive creation * Verbose/quiet output * stdout vs. file output * Manifest file support * Deflation or storage * Changing to directory and adding files (-C) * Archive content listing (-t) * Archive extraction (-x)

Osmosis is a command line java app for processing OSM data. The tool consists of a series of pluggable components that can be chained together to perform a larger operation. For example, it has components for reading from database and from file, components for writing to database and to file, components for deriving and applying change sets to data sources, components for sorting data, etc. It has been written so that it is easy to add new features without re-writing common tasks such as file or database handling.

It shows you the solar system viewed from top (90 heliocentric). The objects have the following colors: Sun - yellow Mercury - green Venus - white Earth - cyan Mars - red Jupiter - gray Saturn - green Uranus - pink Neptune - cyan Pluto is not included since it's way "off course" A left click on the window changes the view between inner and outer planets. A left click on the date increases the day/month/year. A right click on the date does the opposite. Click the right mouse button on the solar system to reset the date to the current date (which is in Universal Time).

Ecasound is a software package designed for multitrack audio processing. It can be used for simple tasks like audio playback, recording and format conversions, as well as for multitrack effect processing, mixing, recording and signal recycling. Ecasound supports a wide range of audio inputs, outputs and effect algorithms. Effects and audio objects can be combined in various ways, and their parameters can be controlled by operator objects like oscillators and MIDI-CCs. As most functionality is located in shared libraries, creating alternative user-interfaces is easy. A versatile console mode interface is included in the package.