Free wikid strong authentication system 2.0 build software for linux

The Contiki Operating System is mostly known as an operating system for networked embedded systems. A few years ago, however, Contikis primary claim to fame was its Commodore 64 port.
With the help of JAC64, a Java-based C64 emulator developed by my colleague and fellow Contiki developer Joakim Eriksson, you can now experience the C64 port of Contiki 1.2-devel1 again, directly in your web browser!
Enhancements:
- Contiki now does dynamic run-time loading and linking of standard ELF files.
- Rime, a protocol stack designed for low-power radio communication, has been added.
- Cooja, a Java-based network simulator for Contiki is included.
- The build system has been reworked to allow for easy cross-compiling for many platforms.
- A new port for the Tmote Sky sensor board has been added.

Sporniket Web Site System project is a set of PHP scripts that allow you to build and manage a Web site.

Two modules are available: Mini File Commander, a Web interface to manage files, and Cabbage, a system to quickly build a Website with organised content without using a database.

slacktrack is a tool to assist with building Slackware packages from the < package >.build scripts that can be found in the distribution source tree.
slacktrack can also be used to build packages where Makefile does not honour any DESTDIR type variable, and enables end-users to create packages more easily.
altertrack is also included with slacktrack. This is a version of slacktrack which does not use installwatch, instead it compares the differences in the file system before and after the build.
slacktrack is based on the idea behind CheckInstall and uses installwatch.
Enhancements:
- A bug in altertracks touch filesystem code has been fixed.

Sin project is a framework that implements Continuous Integration on top of the Subversion version control system.
This can help to improve the overall productivity of your development team by reducing the number of build breakage experiences or even eliminating them entirely.
Main features:
Stable codebase
- Sin ensures that your codebase is stable at all times. Here, stable is defined as the codebase obeying all rules you set up in your Sin system (codebase must build, all tests must pass, etc.).
Sin saves your time
- Developers will never be bothered with the consequences of incorrect changes that cause broken builds. Sin automatically reverts (undoes) any change that violates one or more rules and notifies the developer who checked in the change, of the problem.
Sin is easy to set up and use
- Use the graphical setup application to set up your Sin system in minutes. Once set up, developers hardly know Sin is there until they check in a change that breaks the build - in which case Sin might just have saved the developer from public humiliation.
Easy reviewing
- Sin can send checked in changes in color-coded html by email for easy reviewing by other developers.
Use your existing build system
- No change to your existing build system is needed as long as your system can be built from the command line.
Sin is scalable
- Sin is a distributed system based on open standards like SOAP webservices and is easy to expand to handle new loads.

Mod_Auth_External and mod_authnz_external are Apache modules used for authentication. The two modules provide basically the same functionality, and differ mainly in the way they interface to other authentication code in Apache. For Apache 2.1 and later, mod_authnz_external should be prefered.

The Apache HTTP Daemon can be configured to require users to supply logins and passwords before accessing pages in some directories. Authentication is the process of checking if the password given is correct for a user. Apache has standard modules for authenticating out of several different kinds of databases. These external authentication modules provide a flexible tool for creating authentication systems based on other databases.

These modules can be used in either of two somewhat divergent ways:

External Authentication:

When a user supplies a login and password, mod_auth*_external runs a program you write, passing it the login and password. Your program does whatever checking and logging it needs to, and then returns a Accept/Reject flag to Apache.

This is slower than doing the authentication internally because it has the overhead of launching an external program for each authentication. However, there are at least two situations where it is very useful:

Rapid prototyping. Mod_auth*_external makes a very nice swiss army knife authenticator. You can quickly put together custom authentication systems for many weird authentication applications. The external authentication program can be a shell script or perl program. It can be written without knowing much about building Apache modules. Bugs in it will not endanger the overall integrity of the Apache server.
Access restrictions. There are situations where you do not want to make your user database readable to the user-id that Apache runs under. In these cases the external authentication program can be an suid program that has access to databases Apache cannot access. For example, if you want to authentication out of a Unix shadow password database, and you arent foolish enough to run Apache as root, a carefully written suid-root external authentication program can do the job for you. Such an authenticator for shadow password files and PAM (pwauth) is available separately.

Hardcoded Authentication:

Some hooks have been inserted into mod_auth*_external to make it easy to replace the call to the external authentication program with a call to a hardcoded internal authentication routine that you write.

This is sort of a half-way measure to just writing your own Apache module from scratch, allowing you to easily borrow some of the logic from mod_auth*_external. Its a bit more dangerous than using an external authenticator, as bugs in your module can crash Apache, but performance is usually better.

I think mod_auth*_external is the best current solution for authenticating out of shadow password files, and other similar applications. For rapid prototyping and for an easy way to build your own modules, mod_perl may be a better solution in some cases.

Exact Build project is a sane GNU Auto replacement. For portable build systems nowadays normally GNU autoconf and the associated companiens such as automake and libtool. However albeit portable they are rather crufty to use. The various macro expansion and generation steps extremely blow up the initial definitions and make execution slow and debugging a nightmare.

Even with the enourmous code bloat, it does not have a wide feature set and neither allows to maximize the gain of parallel builds nor other state-of-the-art compiler features. Manual tinkering is needed in such cases.

Mostly due the code bloat but also to obtain features such as mximal parallel build and object output seperated cleanly from the source, we create our own set of Makefiles for the non-recursive build system and shell scripts for configuration, if required by the software module (some straight forware code does come without a configure script at all).

TeleAuth Client Tools are a set of Unix tools for the TeleAuth two-factor/two-channel authentication system.

This includes a commandline client and a set of PAM modules. It also enables out-of-the-box two-factor authentication on Linux, Mac OS X, and Windows machines.

These tools can be used to integrate Web sites, VPNs, and other network services with TeleAuth. They are primarily written for the free Public TeleAuth Server.

This package contains a set of optional (but convenient) client tools for TeleAuth.

Index:

commandline/ - TeleAuth Commandline Client
pam_teleauth/ - PAM modules. Source and some binaries.
demo/ - A CGI-based TeleAuth example for a fictional financial company.
drupal/ - A TeleAuth authentication module for Drupal (http://drupal.org).
ruby/ - The Ruby-TeleAuth module.