Free user folder software for linux

ACASUserFolder is a User Folder implementing the Yale CAS Single Sign On (SSO) Authentication method.
It aims are interoperability, robustness, security and end user simplicity. This project started at the Bordeaux 1 University as a proof of concept for Plone integration in a CASified esup-portal environment.
This Product was formerly known as CASUserFolder but has been renamed to avoid name conflict with another similar product.
Main features:
- Yale CAS architectures 1.0 & 2.0
- Plone Support
- GroupUserFolder support (patch for versions < 3.3)
- Support for POST and GET methods arguments
- Auto-login without adding login button to your site
- clean implementation : doesnt patch anything in the running zope instance
- management tab for testing CAS login
- default roles for CAS Users
- optional persistent users for assigning local roles
- online help
Compatibility:
- python 2.1 (see note below) / 2.2 / 2.3
- Zope : tested with 2.6.2 / 2.7.1 / 2.7.4 / 2.7.5 / 2.8.0 / 2.8.1
- Plone : tested with 2.0.5 & 2.1
- GoupUserFolder (need patch for versions < 3.3)
- CookieCrumbler
- VirtualHostMonster proof (groarrrr)
Installation:
Uncompress the tarball in your Zope Products directory. Under GNU/Linux This is something like:
/usr/lib/zope/lib/python/Products/
Next restart Zope to take the product into account.
Enhancements:
- FIX: deactivated verbose debug output

Aerials-Kde is a KDE style.

Installation:

Extract Aerials-style.tar.bz2:
In Kde control panel import Aerials.kcsrc for color scheme and Aerials.qtcurve for the qtcurve style with custom colors and widgets.

Extract Aerials-deKorator.tar.bz2:
Copy the folder under your deKorator directory (usually /home/YOUR-USER/.kde/share/apps/deKorator/themes)

Extract Aerials-wallpapers.tar.bz2:
Copy the wallpapers in your wallpapers dir! :) Custom them with color gradients for nice effects!

User::Utmp is a Perl access to utmp- and utmpx-style databases.

SYNOPSIS

use User::Utmp qw(:constants :utmpx);
@utmp = getutx();
or, using utmp:
use User::Utmp qw(:constants :utmp);
@utmp = getut();

UNIX systems record information about current and past logins in a user accounting database. This database is realized by two files: File utmpx contains a record of all users currently logged onto the system, while file wtmpx contains a record of all logins and logouts. Some systems (such as HP-UX and AIX) also maintain a third file containing failed login attempts. The information in these files is used by commands such as who(1), last(1), write(1), or login(1).

The exact location of these files in the file system varies between operating systems, but they are typically stored in directories like /var/adm, /var/run, or /var/log. The Single UNIX Specification specifies an API for reading from and writing to these files.

The utmpx file format and functions were derived from the older utmp file format and functions. For compatibility reasons, many systems still support the utmp functions and maintain utmp database files. It is recommended, however, to use the utmpx functions instead of the obsolete utmp functions.
The User::Utmp module provides functions for reading and writing utmpx and utmp files by providing a Perl interface to the system functions.

Utmpx and utmp records are represented in Perl by hash references. The hash keys are the names of the elements of the utmpx structure. For details consult utmpx(4) (utmpx(5) on some systems). The hash values are (mostly) the same as in C.

As an example, here is a typical record as it may be returned by the getutxent(), getutxid(), getutxline() or the corresponding utmp functions:

{ut_tv => {tv_sec => 1141256698, tv_usec => 0},
ut_line => "ttyp0",
ut_time => 1141256698,
ut_id => "p0",
ut_host => ":0.0",
ut_exit => {e_termination => 0, e_exit => 2},
ut_pid => 4577,
ut_user => "mxp",
ut_type => USER_PROCESS,}

The array returned by the getutx() and getut() functions is composed of hash references like this.

mod_auth_user_dir is a module for Apache 2, you can create private user folders using WebDAV protocol. Users have only permissions to access to their own directory. Without this module, a htaccess file must be created inside every user folder. This is completely unmanageable when the number of users is big.

We can build a file server accessible from Windows and Linux using WebDAV and a web server like Apache. Because the protocol is build upon HTTP, the server uses ports TCP 80 (HTTP) and TCP 443 (HTTPS). These ports are commonly open in firewalls without any other special requirement.

User authentication (login and password) are delegated to other Apache modules like mod_auth_ldap.

Installation:

download the binary or compile the source. It should work with all Apache 2.x versions.
install the module with /usr/local/apache2/bin/apxs -i -a -n auth_user_dir libmod_auth_user_dir.la
configure directory options in httpd.conf. Option AUTHUSERDIRROOT can be defined for every Directory, and it is the root folder where user folders will be created.
restart Apache: apachectl restart

GIMP User Manual project is a user manual for the GIMP. It is written for the GIMP Help Browser, but can produce help pages for other formats as well.
Enhancements:
- New content (incl. spelling and grammar fixes) for German, French, Italian, Norwegian, Russian, Spanish and Korean
- The PDF version of the manual is now generated using dblatex
- Lots of bug fixes

User::grent is an interface to Perls built-in getgr*() functions.

SYNOPSIS

use User::grent;
$gr = getgrgid(0) or die "No group zero";
if ( $gr->name eq wheel && @{$gr->members} > 1 ) {
print "gid zero name wheel, with other members";
}

use User::grent qw(:FIELDS);
getgrgid(0) or die "No group zero";
if ( $gr_name eq wheel && @gr_members > 1 ) {
print "gid zero name wheel, with other members";
}

$gr = getgr($whoever);

This modules default exports override the core getgrent(), getgruid(), and getgrnam() functions, replacing them with versions that return "User::grent" objects. This object has methods that return the similarly named structure field name from the Cs passwd structure from grp.h; namely name, passwd, gid, and members (not mem). The first three return scalars, the last an array reference.

You may also import all the structure fields directly into your namespace as regular variables using the :FIELDS import tag. (Note that this still overrides your core functions.) Access these fields as variables named with a preceding gr_. Thus, $group_obj->gid() corresponds to $gr_gid if you import the fields. Array references are available as regular array variables, so @{ $group_obj->members() } would be simply @gr_members.

The getpw() function is a simple front-end that forwards a numeric argument to getpwuid() and the rest to getpwnam().

To access this functionality without the core overrides, pass the use an empty import list, and then access function functions with their full qualified names. On the other hand, the built-ins are still available via the CORE:: pseudo-package.