Free access control systems software for linux

Distributed Access Control System is a complete, light-weight, single sign-on and role-based access control system distributed under an open source license. It provides:
- extended authentication and role-based access control capabilities for Apache-based web services, CGI programs, and virtually any program or script;
- a wide array of flexible, modular, and efficient authentication methods, including two-factor authentication and hardware tokens;
- powerful, rule-based authorization checking that can be applied transparently to any resource or activity (such as web services, web content, and program features) by Apache-based web services and CGI programs, or virtually any program or script;
- an Apache 2.0/2.2 module, suite of CGI programs, and collection of command line tools for Unix-type platforms, such as Linux, FreeBSD, and Solaris.
Enhancements:
- This release includes an important bugfix to local_passwd_authenticate that prevents invalid passwords from being accepted.
- Some minor bugs have also been addressed, including some problems with dacs.quick(7).

The Bazaar Revision Control System is a changeset-oriented revision control system based on Arch that makes it possible to retain previous changes to projects and coordinate development with other developers.
Its goal is to speed development of an upwards- compatible version of Arch.
Main features:
- All the transparent and robust storage features of GNU Arch.
- seamless upgrade path to [WWW] bazaar-ng
- direct support for URLs - one command can checkout or merge from remote locations.
- integrated GPG support - zero setup for most signed archive situations
- faster - checkout, most local operations, commits
- svn-like diff, switch, import, export, log commands
- Explicit tracking of conflicts, preventing accidental commits of files with conflicts
- single merge command that allows merging between arbitrary branches.
- Daily builds of the latest code (Downloads).
- fully compatible with tla - drop in and start using
- supports debian version numbers in branch names
- annotate support
- internationalised via gettext and [WWW] Rosetta.
- Python bindings.
Enhancements:
- More Solaris fixes.
- SSL support and ~/.authinfo support.
- Many UI tweaks.
- A number of bugfixes.

PHP Generic Access Control List is a PHP class that offers Web developers a simple, yet immensely powerful "drop in" permission system for their current Web-based applications.
Main features:
- Split into two classes, and a seperate administration interface.
1. GACL class: Designed to be very small (517 lines of code including comments) and very fast, this class strictly takes care of the permission checks.
2. GACL_API class: Designed to be robust and flexible, this class takes care of creating/editing/deleting objects, groups and ACLs.
3. phpGACL Administration Interface: A set of scripts that allow for the easy administration of the entire GACL universe using only your browser.
- NOT limited to typical "read/write/execute" permissions similar to some flavours of *nix
- User definable "Access Control Objects" (ACO). These are objects which control what access is available to "requesters" (see below).
- Several examples:
- Enable - Projects
- View - Projects, View Own - Projects
- Edit - Projects, Edit Own - Projects
- Delete - Projects, Delete Own - Projects, UnDelete - Projects, UnDelete Own - Projects
- Add - Projects
- System down for Maintenance
- View - The letter "e" ;)
- User definable "Access Request Objects" (ARO). These are objects which request access from an "Access Control Object" (above) examples would be:
- Users/Accounts
- IP Addresses
- Browsers/Browser capabilities (JS/Flash/DHTML)
- User definable "Access eXtension Objects" (AXO). These are objects which extend permissions to a 3rd layer, optionally allowing you to set fine grained permissions on each individual item in your application, or even row in your database. AXOs are often used in cases where you only want to give a user access to a specific project or contact.
- Several examples:
- Projects - Project ID: 3474 (Accounting Software)
- Projects - Project ID: 3484 (Financial Software)
- Contacts - Contact ID: 4775 John Doe
- Contacts - Contact ID: 4795 John Doe
- Tree based ARO/AXO Object grouping with inheritance.
- Contains functionality to easily program add-ons. Examples would be for product pricing, or quantity limitations.
- One function application integration: acl_check()
- Simply pass this function four parameters, it doesnt get any easier!
- Supports the most popular databases using the ADODB database abstraction layer. (MySQL, PostgreSQL, Oracle, MSSQL)
- Complete web based administration interface.
- Scalable. A real-world working version with many added layers of complexity supports over 60,000 Accounts, 200 Groups and 300 ACOs.
Requierments:
- PHP 4.x or greater
- SQL database. (MySQL 3x/4.0.15+, PostgreSQL 7.2+, Oracle 9i+, MS-SQL 2000+)
Enhancements:
- This release contains several minor bugfixes and a fix for a major bug with del_object(), which caused transactions to abort prematurely.
- It also contains a slightly improved installer with Informix support, less possibility of conflicting code with other applications, and upgraded ADODB and Smarty packages.

Rule Set Based Access Control (RSBAC) is a Free Software security extension for current Linux kernels. Rule Set Based Access Control is based on the Generalized Framework for Access Control (GFAC) by Abrams and LaPadula and provides a flexible system of access control based on several modules.
All security relevant system calls are extended by security enforcement code. This code calls the central decision component, which in turn calls all active decision modules and generates a combined decision. This decision is then enforced by the system call extensions.
Main features:
- Free Open Source (GPL) Linux kernel security solution
- Independent of governments and big companies
- Several well-known and new security models, like MAC, ACL and RC
- On-access virus scanning with the Dazuko interface
- Detailed control over individual user and program network accesses
- Fully access controlled kernel level user management
- Any combination of security models possible
- Easily extensible: write your own model for runtime registration
- Support for latest kernels and stable for production use
Enhancements:
- This release relates to kernel 2.4.34.5 and 2.6.22.1.
- There are important fixes with some compilation errors and an important bug with User Management password hashing, introduced with the newer 2.6 kernel crypto API.
- Some security has been added with safety measures against null pointers.

AdaControl is a free (GMGPL) tool that detects the use of various kinds of constructs in Ada programs. AdaControls first goal is to control proper usage of style or programming rules, but it can also be used as a powerful tool to search for use (or non-use) of various forms of programming styles or design patterns. Searched elements range from very simple, like the occurrence of certaine entities, declarations, or statements, to very sophisticated, like verifying that certain programming patterns are being obeyed..
Which elements or constructs are searched is defined by a set of rules; the following table gives a short summary of rules currently checked by AdaControl. The number in parentheses after the rule name gives the number of subrules, if any. Considering all possible rules and subrules, this makes 216 tests that can be performed currently by AdaControl!
- Abnormal_Function_Return Controls a design pattern that ensures that a function always returns a result .
- Allocators Controls ocurrences of allocators, either all of them, or those targeting specified types.
- Array_Declarations (x2) Controls several metrics in array declarations.
- Barrier_Expressions Controls elements allowed in the expression of protected entries barriers
- Case_Statement (x4) Controls several metrics in case statements.
- Control_Characters Controls occurrences of control characters (like tabs) in the source.
- Declarations (x75) Controls occurrences of certain Ada declarations.
- Default_Parameter Controls subprogram calls and generic instantiations that use (or not) the default value for a given parameter.
- Directly_Accessed_Globals Controls a design pattern that ensures that all global variables are accessed only through dedicated subprograms.
- Entities Controls occurrences of any Ada entity.
- Entity_Inside_Exception Controls occurrences of entities inside exception handlers.
- Exception_Propagation (x4) Controls that certain subprograms (or tasks) cannot propagate exceptions, or that no elaboration can propagate exceptions.
- Expressions (x9) Controls usage of certain forms of expressions
- Global_References Controls unsynchronized accesses to global variables.
- Header_Comments (x2) Controls the presence of comments at the start of each module.
- If_For_Case Controls if statements that could be replaced by case statements.
- Instantiations Controls generic instantiations, either all of them, or those that use specified entities.
- Insufficient_Parameters Controls the use of positional parameters in calls where the value does not provide sufficient information.
- Local_Hiding Controls occurrences of local identifiers that hide an identical outer one.
- Local_Instantiation Controls instantiations in local scopes.
- Max_Blank_Lines Controls the occurrence of more than a specified number of consecutive empty lines.
- Max_Call_Depth Controls the maximum depth of subprogram calls.
- Max_Line_Length Controls maximal length of source lines.
- Max_Nesting Controls scopes nested more deeply than a given limit.
- Max_Parameters (x6) Controls the maximum numbers of parameters in callable entities (procedures, functions and entries)
- Max_Statement_Nesting (x5) Controls composite statements nested more deeply than a given limit.
- Movable_Accept_Statements Controls statements that could be moved outside an accept statement.
- Naming_Convention Controls the form of allowed (or forbidden) names in declarations.
- No_Safe_Initialization Controls a design pattern that ensures that any variable is initialized before being used.
- Non_Static (x3) Controls non static expressions in index or discriminant constraints, or in instantiations.
- Not_Elaboration_Calls Controls subprogram calls performed from places outside package elaboration code.
- Other_Dependencies Controls semantic dependencies to other units than those indicated
- Parameter_Aliasing Controls subprograms and entry calls where a variable is provided to more than one [in] out parameter.
- Potentially_Blocking_Operations Controls the use of potentially blocking operations from within protected operations.
- Pragmas Controls the use of specific pragmas.
- Real_Operators Controls occurrences of = or /= operators on real types.
- Reduceable_Scope Controls declarations that could be move to more deeply nested scopes.
- Representation_Clauses Controls occurrences of representation clauses.
- Return_Type Controls the use of certain kinds of types as return types of functions.
- Side_Effect_Parameters Controls subprogram calls and generic instantiations that call functions with side effect, thus creating a dependance to the order of evaluation.
- Silent_Exceptions Controls exception handlers that do not reraise exceptions nor call indicated subprograms.
- Simplifiable_Expressions (x4) Controls occurrences of various forms of expressions that could be simplified.
- Special_Comments Controls the presence of certain string patterns in comments.
- Statements (x42) Controls occurrences of Ada statements.
- Style (x12) Controls various forms of constructs generally recommended in style rules.
- Terminating_Tasks Controls a design pattern that ensures that tasks never terminate.
- Uncheckable (x3) Controls constructs that are not statically checkable by other rules
- Unnecessary_Use_Clause Controls use clauses on packages, where no element of the package is referred to within the scope of the use clause.
- Unsafe_Paired_Calls Controls a design pattern that ensures that certain calls are allways paired (like P/V procedures).
- Unsafe_Unchecked_Conversion Controls instantiations of Unchecked_Conversion between types of different or unspecified sizes.
- Usage (x5) Controls usage of objects under certain conditions (in package specifications, read, written modified...).
- Use_Clauses Controls occurrences of use clauses, except for indicated packages.
- With_Clauses (x3) Controls proper usage of with clauses.
Enhancements:
- This release adds rules to check that header comments match a given pattern.
- It has indication of possible false positives and false negatives due to non-statically analyzable constructs.
- There is a fine definition of constructs allowed in entry barriers (including the one of the Ravenscar profile).
- There is better integration into GPS, and much more.

XMMS-Control provides a Web-based control for XMMS.
XMMS-Control is a web-based interface for the XMMS (X MultiMedia System). XMMS is an MP3 player for Linux based systems (it also plays other media formats).
XMMS-Control is a graphical interface for the command-line utility XMMS-Shell.
Using XMMS-Control, you can control the music playng from an XMMS equipped machine from any PC on the network, including wireless laptops/PDAs!!!
Imagine being out in the pool and being able to control the music with an 802.11b based PocketPC using a browser! You can do it with XMMS-Control!
XMMS-Control has an interface for standard PCs (desktops/laptops), as well as a mobile/PDA formatted interface, for smaller screens!!!
In addition, XMMS-Control can itself be controlled via other programs (i.e., custom interfaces) using the XMMS-Control API/Hooks program! You can tie XMMS-Control into a larger system via this method.
Lets say youre creating a system for whole-house automation, and you wish to use ONE consistent interface. Well, with the XMMS-Control API/Hooks, you can!!!
Enhancements:
- Some major bugfixes... should work MUCH BETTER on most platforms that had problems before. If you had problems getting XMMS-Control installed and running, please try this new version! Please read the new installation entries in the manual!!!
- More detailed installation instructions for getting XMMS-Shell up and running (including V0.99) in the README & manual.
- Directories are now SORTED alphabetically on the file chooser screen (previously was unsorted).
- Should handle MP3 lists with file names and ID3 tags containing commas much better now (previously when a comma was encountered, the list was off by one, the name would get split, and the second half would go to the next line).

Coda is an advanced networked filesystem. The project has been developed at CMU since 1987 by the systems group of M. Satyanarayanan. in the SCS department.
Coda is a distributed filesystem with its origin in AFS2. It has many features that are very desirable for network filesystems. Currently, Coda has several features not found elsewhere.
1. disconnected operation for mobile computing
2. is freely available under a liberal license
3. high performance through client side persistent caching
4. server replication
5. security model for authentication, encryption and access control
6. continued operation during partial network failures in server network
7. network bandwith adaptation
8. good scalability
9. well defined semantics of sharing, even in the presence of network failures
Enhancements:
- Coda now works on 64-bit systems.
- The client and server were successfully built and used on a machine with em64t extensions with a 64-bit Linux kernel.
- The new RVM-1.14 and RPC2-2.5 releases also incorporate some essential 64-bit fixes.
- Another welcome change is that venus now tries to keep cached access rights available for users even across system reboots or client restarts, which should improve life for people who frequently shut down or dual boot their machines.

active acoustic vibration control tool is a set of basic tools for monitoring and modulating audio noise.

The tools aim toward a set of codes and algorithms for monitoring noise signal and modulation and reducing them using active noise control priciples.

Active noise control and soundproofing is a relativly recent development (first researched around 30 years ago), and has been in constant development for many and varied situations and applications.

The basic concept of active noise control is the aplication of equal and opposite force to cancel out vibration.

The project attempts to provide a starting point and library for experimentation into various methods of digital signal processing for active noise reduction and soundproofing.

Noise cancellation has been used in many environments currently active control is best used in constant vibrations with lower frequencys.

The principle is of controlling the noise level by adding an equal and opposite sound to the noise in the environment. The basic principle may be simple but the actual effectivness depends on many environmental factors.

Generally simplistic out of phase sound wave is used which works to some extent and requires little processing (a simple XOR with -1) this will tend to leave a large number of artifacts as the amplitude of higher frequency components (above i->o delay time) rises.

i->o processing delay
e transducer efficiency
p sound propagation characteristics
r reflections

The project aims to provide a framework for many dsp architectures, dac/adc chips, transducers and monitors.

Create tools for acoustic calibration and data logging hardware
To simplify implementation of active noise and vibration control systems.
To provide an open source standard for use within the industry and education.
To encourage hardware producers to distribute standard interface descriptions for their hardware
Enable low cost development of systems using COTS consumer hardware for noise and vibration control.