user
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 6917
User::Utmp 1.8
User::Utmp is a Perl access to utmp- and utmpx-style databases. more>>
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.
<<lessSYNOPSIS
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.
Download (0.011MB)
Added: 2007-04-10 License: Perl Artistic License Price:
929 downloads
TuxUsers 0.6.0
TuxUsers application is a user management KControl module and stand alone utility. more>>
TuxUsers application is a user management KControl module and stand alone utility.
It allows very wasy user accounts management:
- User creation, deletion and modification.
- Change KDM start icon.
- Predefined groups for new users to ease new user permissions.
- Thinkfinger fingerprint reader suported to add easily fingerprint auth. for your system.
<<lessIt allows very wasy user accounts management:
- User creation, deletion and modification.
- Change KDM start icon.
- Predefined groups for new users to ease new user permissions.
- Thinkfinger fingerprint reader suported to add easily fingerprint auth. for your system.
Download (0.13MB)
Added: 2007-07-25 License: GPL (GNU General Public License) Price:
824 downloads
User::pwent 5.8.8
User::pwent is a Perl interface getpw*() functions. more>>
User::pwent is a Perl interface getpw*() functions.
SYNOPSIS
use User::pwent;
$pw = getpwnam(daemon) || die "No daemon user";
if ( $pw->uid == 1 && $pw->dir =~ m#^/(bin|tmp)?z#s ) {
print "gid 1 on root dir";
}
$real_shell = $pw->shell || /bin/sh;
for (($fullname, $office, $workphone, $homephone) =
split /s*,s*/, $pw->gecos)
{
s/&/ucfirst(lc($pw->name))/ge;
}
use User::pwent qw(:FIELDS);
getpwnam(daemon) || die "No daemon user";
if ( $pw_uid == 1 && $pw_dir =~ m#^/(bin|tmp)?z#s ) {
print "gid 1 on root dir";
}
$pw = getpw($whoever);
use User::pwent qw/:DEFAULT pw_has/;
if (pw_has(qw[gecos expire quota])) { .... }
if (pw_has("name uid gid passwd")) { .... }
print "Your struct pwd has: ", scalar pw_has(), "n";
This modules default exports override the core getpwent(), getpwuid(), and getpwnam() functions, replacing them with versions that return User::pwent objects. This object has methods that return the similarly named structure field name from the Cs passwd structure from pwd.h, stripped of their leading "pw_" parts, namely name, passwd, uid, gid, change, age, quota, comment, class, gecos, dir, shell, and expire. The passwd, gecos, and shell fields are tainted when running in taint mode.
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 pw_ in front their method names. Thus, $passwd_obj->shell corresponds to $pw_shell if you import the fields.
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. The built-ins are always still available via the CORE:: pseudo-package.
<<lessSYNOPSIS
use User::pwent;
$pw = getpwnam(daemon) || die "No daemon user";
if ( $pw->uid == 1 && $pw->dir =~ m#^/(bin|tmp)?z#s ) {
print "gid 1 on root dir";
}
$real_shell = $pw->shell || /bin/sh;
for (($fullname, $office, $workphone, $homephone) =
split /s*,s*/, $pw->gecos)
{
s/&/ucfirst(lc($pw->name))/ge;
}
use User::pwent qw(:FIELDS);
getpwnam(daemon) || die "No daemon user";
if ( $pw_uid == 1 && $pw_dir =~ m#^/(bin|tmp)?z#s ) {
print "gid 1 on root dir";
}
$pw = getpw($whoever);
use User::pwent qw/:DEFAULT pw_has/;
if (pw_has(qw[gecos expire quota])) { .... }
if (pw_has("name uid gid passwd")) { .... }
print "Your struct pwd has: ", scalar pw_has(), "n";
This modules default exports override the core getpwent(), getpwuid(), and getpwnam() functions, replacing them with versions that return User::pwent objects. This object has methods that return the similarly named structure field name from the Cs passwd structure from pwd.h, stripped of their leading "pw_" parts, namely name, passwd, uid, gid, change, age, quota, comment, class, gecos, dir, shell, and expire. The passwd, gecos, and shell fields are tainted when running in taint mode.
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 pw_ in front their method names. Thus, $passwd_obj->shell corresponds to $pw_shell if you import the fields.
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. The built-ins are always still available via the CORE:: pseudo-package.
Download (12.2MB)
Added: 2007-04-10 License: Perl Artistic License Price:
928 downloads
User::grent 5.8.8
User::grent is an interface to Perls built-in getgr*() functions. more>>
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.
<<lessSYNOPSIS
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.
Download (12.2MB)
Added: 2007-04-10 License: Perl Artistic License Price:
927 downloads
dtRdr::User 0.0.11
dtRdr::User.pm is a user class as a Perl module. more>>
dtRdr::User.pm is a user class as a Perl module.
Constructor
new
$user = dtRdr::User->new($username);
Methods
init_config
$user->init_config($filename);
<<lessConstructor
new
$user = dtRdr::User->new($username);
Methods
init_config
$user->init_config($filename);
Download (2.8MB)
Added: 2007-03-16 License: GPL (GNU General Public License) Price:
954 downloads
Apache Users 1.0
Apache Users project is an Apache username enumerator, via /~username requests. more>>
Apache Users project is an Apache username enumerator, via /~username requests. This script uses a list of common system names like root, admin etc ...
You should manually check the issue to establish the http return code, ie: 403 as this is needed for the command line. No native SSL support.
USAGE apache.pl -h 1.2.3.4 -l names -p 80 (No SSL Support) -e 403 (http code)
Sample script:
use IO::Socket;
use Getopt::Std;
getopt ("h: l: p: e: ");
use vars qw( $opt_h $opt_l $opt_p $opt_e );
if ((! $opt_h) || (! $opt_l ) || (! $opt_p ) || (! $opt_e)) {
print "nUSAGE: apache.pl -h 1.2.3.4 -l names -p 80 (No SSL Support) -e 403 (http code)nn ";
exit 1;
};
$host = $opt_h;
$list = $opt_l;
$port = $opt_p;
$num = $opt_e;
open (LIST, "$list") or die "Unable to open $list ....$!";
&connect;
exit 0;
sub connect {
foreach $name (< LIST >) {
$connection = IO::Socket::INET->new (
Proto => "tcp",
PeerAddr => "$host",
PeerPort => "$port",
) or die "Cant CONNECT to $host on the Port specified.n";
$connection -> autoflush;
chomp $name;
print $connection "GET /~$name HTTP/1.0rnrn";
$results = < $connection >;
if ( $results =~/($num)/g ) {
print "$name exists on $hostn";
};
}
close ($connection);
sleep 1;
};
close LIST;
<<lessYou should manually check the issue to establish the http return code, ie: 403 as this is needed for the command line. No native SSL support.
USAGE apache.pl -h 1.2.3.4 -l names -p 80 (No SSL Support) -e 403 (http code)
Sample script:
use IO::Socket;
use Getopt::Std;
getopt ("h: l: p: e: ");
use vars qw( $opt_h $opt_l $opt_p $opt_e );
if ((! $opt_h) || (! $opt_l ) || (! $opt_p ) || (! $opt_e)) {
print "nUSAGE: apache.pl -h 1.2.3.4 -l names -p 80 (No SSL Support) -e 403 (http code)nn ";
exit 1;
};
$host = $opt_h;
$list = $opt_l;
$port = $opt_p;
$num = $opt_e;
open (LIST, "$list") or die "Unable to open $list ....$!";
&connect;
exit 0;
sub connect {
foreach $name (< LIST >) {
$connection = IO::Socket::INET->new (
Proto => "tcp",
PeerAddr => "$host",
PeerPort => "$port",
) or die "Cant CONNECT to $host on the Port specified.n";
$connection -> autoflush;
chomp $name;
print $connection "GET /~$name HTTP/1.0rnrn";
$results = < $connection >;
if ( $results =~/($num)/g ) {
print "$name exists on $hostn";
};
}
close ($connection);
sleep 1;
};
close LIST;
Download (0.023MB)
Added: 2007-04-05 License: GPL (GNU General Public License) Price:
933 downloads
User::Identity 0.91
User::Identity is a Perl module that maintains info about a physical person. more>>
User::Identity is a Perl module that maintains info about a physical person.
INHERITANCE
User::Identity
is an User::Identity::Item
SYNOPSIS
use User::Identity;
my $me = User::Identity->new
( john
, firstname => John
, surname => Doe
);
print $me->fullName # prints "John Doe"
print $me; # same
The User::Identity object is created to maintain a set of informational objects which are related to one user. The User::Identity module tries to be smart providing defaults, conversions and often required combinations.
The identities are not implementing any kind of storage, and can therefore be created by any simple or complex Perl program. This way, it is more flexible than an XML file to store the data. For instance, you can decide to store the data with Data::Dumper, Storable, DBI, AddressBook or whatever. Extension to simplify this task are still to be developed.
If you need more kinds of user information, then please contact the module author.
<<lessINHERITANCE
User::Identity
is an User::Identity::Item
SYNOPSIS
use User::Identity;
my $me = User::Identity->new
( john
, firstname => John
, surname => Doe
);
print $me->fullName # prints "John Doe"
print $me; # same
The User::Identity object is created to maintain a set of informational objects which are related to one user. The User::Identity module tries to be smart providing defaults, conversions and often required combinations.
The identities are not implementing any kind of storage, and can therefore be created by any simple or complex Perl program. This way, it is more flexible than an XML file to store the data. For instance, you can decide to store the data with Data::Dumper, Storable, DBI, AddressBook or whatever. Extension to simplify this task are still to be developed.
If you need more kinds of user information, then please contact the module author.
Download (0.025MB)
Added: 2007-04-11 License: Perl Artistic License Price:
926 downloads
Open as user 0.1.4
Open as user is a servicemenu allows you to open a file as a different user. more>>
Open as user is a servicemenu allows you to open a file as a different user.
Installation:
To install, put the file in ~/.kde/share/apps/konqueror/servicemenus and restart Konqueror.
<<lessInstallation:
To install, put the file in ~/.kde/share/apps/konqueror/servicemenus and restart Konqueror.
Download (MB)
Added: 2007-04-04 License: GPL (GNU General Public License) Price:
934 downloads
qmail-masq-user 0.2.1
qmail-masq-user provides a program to change From: field of emails to any combinations of user/domain. more>>
qmail-masq-user provides a program to change From: field of emails to any combinations of user/domain.
Originally based off the program qmail-masq, qmail-masq-user uses qmail and qmail-qfilter to change the From: address of outgoing emails to almost any combination of username, domain, or both.
The configuration allows you to specify domain catch-alls, user catch-alls, email catch-alls, specific combinations of users and/or domains, and much more.
INSTALLATON:
1) install and configure qmail
2) install qmail-qfilter
3) copy qmail-masq-user.conf.example to /etc/qmail-masq.conf and modify it for your
needs (follow the instructions in the file)
# cp qmail-masq-user.conf.example /etc/qmail-masq-user.conf
# chmod 644 /etc/qmail-masq-user.conf
# vi /etc/qmail-masq-user.conf
4) run the install.pl included installer which will set up the files exactly
to be able to run them
# perl install.pl
4) all is done, you dont have to restart qmail, try it sending some email
and enjoy it!
Note: make sure you are root when you install everything!
<<lessOriginally based off the program qmail-masq, qmail-masq-user uses qmail and qmail-qfilter to change the From: address of outgoing emails to almost any combination of username, domain, or both.
The configuration allows you to specify domain catch-alls, user catch-alls, email catch-alls, specific combinations of users and/or domains, and much more.
INSTALLATON:
1) install and configure qmail
2) install qmail-qfilter
3) copy qmail-masq-user.conf.example to /etc/qmail-masq.conf and modify it for your
needs (follow the instructions in the file)
# cp qmail-masq-user.conf.example /etc/qmail-masq-user.conf
# chmod 644 /etc/qmail-masq-user.conf
# vi /etc/qmail-masq-user.conf
4) run the install.pl included installer which will set up the files exactly
to be able to run them
# perl install.pl
4) all is done, you dont have to restart qmail, try it sending some email
and enjoy it!
Note: make sure you are root when you install everything!
Download (0.011MB)
Added: 2007-03-13 License: GPL (GNU General Public License) Price:
959 downloads
Gimp User Manual 0.12
GIMP User Manual project is a user manual for the GIMP. more>>
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
<<lessEnhancements:
- 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
Download (40MB)
Added: 2007-03-08 License: (FDL) GNU Free Documentation License Price:
975 downloads
gnome-user-share 0.11
gnome-user-share binds together various free software projects to bring easy to use user-level file sharing. more>>
gnome-user-share is a small package that binds together various free software projects to bring easy to use user-level file sharing to the masses.
gnome-user-share is meant to run in the background when the user is logged in, and when file sharing is enabled a webdav server is started that shares the $HOME/Public folder. The share is then published to all computers on the local network using mDNS/rendezvous, so that it shows up in the Network location in Gnome.
The dav server used is apache, so you need that installed. Howl is used for mDNS support, so you need to have that installed and mDNSResolver running.
<<lessgnome-user-share is meant to run in the background when the user is logged in, and when file sharing is enabled a webdav server is started that shares the $HOME/Public folder. The share is then published to all computers on the local network using mDNS/rendezvous, so that it shows up in the Network location in Gnome.
The dav server used is apache, so you need that installed. Howl is used for mDNS support, so you need to have that installed and mDNSResolver running.
Download (0.38MB)
Added: 2007-03-06 License: GPL (GNU General Public License) Price:
964 downloads
Samba::LDAP::User 0.03
Samba::LDAP::User is a Perl module to manipulate a Samba LDAP User. more>>
Samba::LDAP::User is a Perl module to manipulate a Samba LDAP User.
SYNOPSIS
use Carp;
use Samba::LDAP::User;
# create Template object
my $user = Samba::LDAP::User->new()
or croak "Cant create objectn";
Various methods to manipulate a Samba LDAP user. Add, delete, modify, show and change a users password.
INTERFACE
new
Create a new Samba::LDAP::User object
add_user
Takes many options. For example:
user =>
oldpass =>
newpass =>
workstation =>
ou =>
user_uid =>
group =>
windows_user =>
trust_account =>
homedir =>
shell =>
gecos =>
skeleton_dir =>
surname =>
family_name =>
local_mail_address =>
mail_to_address =>
time_to_wait =>
aix =>
groups =>
ox =>
can_change_pass =>
must_change_pass =>
account_flags =>
logon_script =>
home_path =>
home_drive =>
user_profile =>
aix_user =>
The above options are only needed if you dont want to use the defaults that are set in /etc/smbldap/smbldap.conf
delete_user
disable_user
is_valid_user
is_samba_user
is_unix_user
is_nonldap_unix_user
get_homedir
make_hash
change_password
change_password(
user => ghenry,
oldpass => "$oldpass",
newpass => "$newpass",
samba => 1, # Update only Samba pass, can be
# unix => 1 for unix pass only
);
Change user password in LDAP Directory
Checks the users exists first, then changes the password If user doesnt exist, returns the error etc.
If no oldpass arg is passed, binds as rootdn and sets a password
Default is set to change/add a Samba "and" Unix password. If you dont want this, pass in unix => 0, or samba => 0, etc.
<<lessSYNOPSIS
use Carp;
use Samba::LDAP::User;
# create Template object
my $user = Samba::LDAP::User->new()
or croak "Cant create objectn";
Various methods to manipulate a Samba LDAP user. Add, delete, modify, show and change a users password.
INTERFACE
new
Create a new Samba::LDAP::User object
add_user
Takes many options. For example:
user =>
oldpass =>
newpass =>
workstation =>
ou =>
user_uid =>
group =>
windows_user =>
trust_account =>
homedir =>
shell =>
gecos =>
skeleton_dir =>
surname =>
family_name =>
local_mail_address =>
mail_to_address =>
time_to_wait =>
aix =>
groups =>
ox =>
can_change_pass =>
must_change_pass =>
account_flags =>
logon_script =>
home_path =>
home_drive =>
user_profile =>
aix_user =>
The above options are only needed if you dont want to use the defaults that are set in /etc/smbldap/smbldap.conf
delete_user
disable_user
is_valid_user
is_samba_user
is_unix_user
is_nonldap_unix_user
get_homedir
make_hash
change_password
change_password(
user => ghenry,
oldpass => "$oldpass",
newpass => "$newpass",
samba => 1, # Update only Samba pass, can be
# unix => 1 for unix pass only
);
Change user password in LDAP Directory
Checks the users exists first, then changes the password If user doesnt exist, returns the error etc.
If no oldpass arg is passed, binds as rootdn and sets a password
Default is set to change/add a Samba "and" Unix password. If you dont want this, pass in unix => 0, or samba => 0, etc.
Download (0.080MB)
Added: 2007-01-12 License: Perl Artistic License Price:
1024 downloads
gnome-user-docs 2.18.2
gnome-user-docs package contains documents which will be packaged together and shipped as gnome-user-docs. more>>
gnome-user-docs package contains documents which will be packaged together and
shipped as gnome-user-docs in the core GNOME distribution.
They should be documents targetted for end-users of GNOME.
Installation:
The simplest way to compile this package is:
1. `cd to the directory containing the packages source code and type ./configure to configure the package for your system. If youre using `csh on an old version of System V, you might need to type `sh ./configure instead to prevent `csh from trying to execute `configure itself.
Running `configure takes awhile. While running, it prints some messages telling which features it is checking for.
2. Type `make to compile the package.
3. Optionally, type `make check to run any self-tests that come with the package.
4. Type `make install to install the programs and any data files and documentation.
5. You can remove the program binaries and object files from the source code directory by typing `make clean. To also remove the files that `configure created (so you can compile the package for a different kind of computer), type `make distclean. There is also a `make maintainer-clean target, but that is intended mainly for the packages developers. If you use it, you may have to get all sorts of other programs in order to regenerate files that came with the distribution.
Enhancements:
Accessibility Guide:
Updated translations:
- es (Jorge Gonzalez)
System Admin Guide:
Updated translations:
- es (Jorge Gonzalez)
User Guide:
Updated translations:
- es (Jorge Gonzalez)
- hu (Gabor Kelemen)
- ko (Changwoo Ryu)
- pa (A S Alam)
- pt (Duarte Loreto)
- pt_BR (Leonardo Ferreira Fontenelle, Vladimir Melo,
- Andre Noel, Felipe Ferreira, Vinicus Pinheiro)
<<lessshipped as gnome-user-docs in the core GNOME distribution.
They should be documents targetted for end-users of GNOME.
Installation:
The simplest way to compile this package is:
1. `cd to the directory containing the packages source code and type ./configure to configure the package for your system. If youre using `csh on an old version of System V, you might need to type `sh ./configure instead to prevent `csh from trying to execute `configure itself.
Running `configure takes awhile. While running, it prints some messages telling which features it is checking for.
2. Type `make to compile the package.
3. Optionally, type `make check to run any self-tests that come with the package.
4. Type `make install to install the programs and any data files and documentation.
5. You can remove the program binaries and object files from the source code directory by typing `make clean. To also remove the files that `configure created (so you can compile the package for a different kind of computer), type `make distclean. There is also a `make maintainer-clean target, but that is intended mainly for the packages developers. If you use it, you may have to get all sorts of other programs in order to regenerate files that came with the distribution.
Enhancements:
Accessibility Guide:
Updated translations:
- es (Jorge Gonzalez)
System Admin Guide:
Updated translations:
- es (Jorge Gonzalez)
User Guide:
Updated translations:
- es (Jorge Gonzalez)
- hu (Gabor Kelemen)
- ko (Changwoo Ryu)
- pa (A S Alam)
- pt (Duarte Loreto)
- pt_BR (Leonardo Ferreira Fontenelle, Vladimir Melo,
- Andre Noel, Felipe Ferreira, Vinicus Pinheiro)
Download (6.9MB)
Added: 2007-07-02 License: LGPL (GNU Lesser General Public License) Price:
844 downloads
XML User Profiles 0.2.3
XML User Profiles is a system that allows for remote and transferable user accounts. more>>
XUP is an attempt to replace static per-site user accounts, which most present dynamic web sites use in absence of an easy to use and open/shared user account system. It allows people to use a single account or profile with many sites, or one of their existing user profiles on multiple other web sites.
It is best suited to so called "community" sites, where the account serves mainly for lax identification of people among each other. It does not stipulate strong authentication (while OpenID or LID can be used) and is therefore only useful for applications with mediocre security and privacy demands.
Chat and discussion sites are the main target, but profiles in different applications can often also be enriched with them. They are meant to get used secondarily (as alternative) to static/local user accounts.
The XML format of user profiles is extremely simple, as is the associated login service API. Both are outlined and explained in the introduction (HTML). The format is basically an XMLified vCard with a few additions targetted at online/web communities. It is easy to parse and generate and therefore also suitable for profile exchange or import.
Theres also a more authoritative RFC-style text version of the current proposal, which provides further hints and explanations for implementors. Future extensions will get listed in the project Wiki however (field names in the XUP format are not regulated).
This effort is quite new, and therefore only very few actual (real-world) implementations are known so far.
Some software, like discussion boards (which mostly suffer from spaghetti code), are of course hard to extent with XML User Profiles. Even those that abstract their internal user database and UI logic reasonably well can often be difficult to adapt. It is however expected that the more professional systems will sooner than later be XUP compatible.
<<lessIt is best suited to so called "community" sites, where the account serves mainly for lax identification of people among each other. It does not stipulate strong authentication (while OpenID or LID can be used) and is therefore only useful for applications with mediocre security and privacy demands.
Chat and discussion sites are the main target, but profiles in different applications can often also be enriched with them. They are meant to get used secondarily (as alternative) to static/local user accounts.
The XML format of user profiles is extremely simple, as is the associated login service API. Both are outlined and explained in the introduction (HTML). The format is basically an XMLified vCard with a few additions targetted at online/web communities. It is easy to parse and generate and therefore also suitable for profile exchange or import.
Theres also a more authoritative RFC-style text version of the current proposal, which provides further hints and explanations for implementors. Future extensions will get listed in the project Wiki however (field names in the XUP format are not regulated).
This effort is quite new, and therefore only very few actual (real-world) implementations are known so far.
Some software, like discussion boards (which mostly suffer from spaghetti code), are of course hard to extent with XML User Profiles. Even those that abstract their internal user database and UI logic reasonably well can often be difficult to adapt. It is however expected that the more professional systems will sooner than later be XUP compatible.
Download (0.23MB)
Added: 2005-07-08 License: GPL (GNU General Public License) Price:
1570 downloads
Group User Folder 3.54.2
Group User Folder provides a Zope Product that manages Groups of Users. more>>
Group User Folder provides a Zope Product that manages Groups of Users.
GroupUserFolder is a kind of user folder that provides a special kind of user management. Some users are "flagged" as GROUP and then normal users will be able to belong to one or serveral groups.
Enhancements:
- Fix _getMemberIds for LDAPUserFolder 2.7 when groups are stored in LDAPUF [encolpe]
- Got rid of zLOG in favor of logging. [stefan]
<<lessGroupUserFolder is a kind of user folder that provides a special kind of user management. Some users are "flagged" as GROUP and then normal users will be able to belong to one or serveral groups.
Enhancements:
- Fix _getMemberIds for LDAPUserFolder 2.7 when groups are stored in LDAPUF [encolpe]
- Got rid of zLOG in favor of logging. [stefan]
Download (0.50MB)
Added: 2007-02-09 License: GPL (GNU General Public License) Price:
988 downloads
Secleted [ 0 ] software to compare
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above user search only lists software in full, demo and trial versions for free download. Download links are directly from our mirror sites or publisher sites, torrent files or links from rapidshare.com, yousendit.com or megaupload.com are not allowed
