user logins
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 6845
Secure Login 0.7.2
Secure Login provides a login extension similar to Operas Wand login. more>>
Secure Login provides a login extension similar to Operas Wand login.
It uses the built-in password manager, but deactivates the prefilling of login forms.
Instead, you are now able to login with one click or a keyboard shortcut (ALT+N).
Just add the Secure Login toolbar button to your toolbar, or use the provided statusbar icon.
If you hover over one of the icons, a tooltip is shown, displaying the login url and the number of available logins (users).
For more than one user or login forms on the current page a selection prompt is displayed on login.
You have the option to play sound notifications (*.wav) for found login data on the current page or when logging in.
All the options can be changed using the Secure Login settings menu or the statusbar icon context menu.
Secure Login provides you with a number of Security enhancements and helps protecting you from phishing:
Disabling the prefilling of login forms prevents malicious JavaScript code to automatically steal your login data.
This is due to the fact that no login data is inserted in form fields before the user clicks on the login button or logs in using the keyboard shortcut.
To make sure you login to the right website, the second level domain of the login url is compared to the second level domain of the current page.
If they do not match a dialog prompt is displayed before login.
SecureLogin provides you with an optional setting to protect you from all JavaScript code during login.
This can prevent cross-site scripting (XSS) attacks without having to deactivate JavaScript completely.
If you enable this option, your login data will never be inserted in any form fields nor will the login form be submitted.
Instead your credentials will be sent to the login page using internal Firefox methods.
Not all login forms will work this way, e.g. not those using JavaScript routines.
Therefore, you can add such websites to an exception list.
<<lessIt uses the built-in password manager, but deactivates the prefilling of login forms.
Instead, you are now able to login with one click or a keyboard shortcut (ALT+N).
Just add the Secure Login toolbar button to your toolbar, or use the provided statusbar icon.
If you hover over one of the icons, a tooltip is shown, displaying the login url and the number of available logins (users).
For more than one user or login forms on the current page a selection prompt is displayed on login.
You have the option to play sound notifications (*.wav) for found login data on the current page or when logging in.
All the options can be changed using the Secure Login settings menu or the statusbar icon context menu.
Secure Login provides you with a number of Security enhancements and helps protecting you from phishing:
Disabling the prefilling of login forms prevents malicious JavaScript code to automatically steal your login data.
This is due to the fact that no login data is inserted in form fields before the user clicks on the login button or logs in using the keyboard shortcut.
To make sure you login to the right website, the second level domain of the login url is compared to the second level domain of the current page.
If they do not match a dialog prompt is displayed before login.
SecureLogin provides you with an optional setting to protect you from all JavaScript code during login.
This can prevent cross-site scripting (XSS) attacks without having to deactivate JavaScript completely.
If you enable this option, your login data will never be inserted in any form fields nor will the login form be submitted.
Instead your credentials will be sent to the login page using internal Firefox methods.
Not all login forms will work this way, e.g. not those using JavaScript routines.
Therefore, you can add such websites to an exception list.
Download (0.059MB)
Added: 2007-04-10 License: MPL (Mozilla Public License) Price:
947 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
Passwordless remote logins 1.02
Passwordless remote logins is a Kommander script that can create 1024 bit passwordless dsa keys. more>>
Passwordless remote logins script can be used to:
1: Create 1024 bit passwordless dsa keys.
2: Send key to remote server via scp.
3: Create remote .ssh directory and move key to authorized_keys file.
This will allow you to login to remote server via ssh or run automated rsync backups. You need openssh, bash and expect installed for this to work. Optionally you can create an executeButton with the following format for a one click remote server login.
The format: konsole -e ssh -i /your/path/toyour-key remoteusername"@"remotehost_or_ip
<<less1: Create 1024 bit passwordless dsa keys.
2: Send key to remote server via scp.
3: Create remote .ssh directory and move key to authorized_keys file.
This will allow you to login to remote server via ssh or run automated rsync backups. You need openssh, bash and expect installed for this to work. Optionally you can create an executeButton with the following format for a one click remote server login.
The format: konsole -e ssh -i /your/path/toyour-key remoteusername"@"remotehost_or_ip
Download (0.041MB)
Added: 2006-03-13 License: GPL (GNU General Public License) Price:
1326 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
locations 1.1
locations project can keep track of user logins. more>>
locations project can keep track of user logins. It is a simple script which can be used to display the locations from which users logged onto your machine from.
This was inspired by a similar script discussed in the Perl For System Administration book from O Reilly.
By default this script will display all the users who have logged into your box from more than three distinct locations - this may be tweaked via the --count=N argument.
Alternatively you may ask for a report on all the hosts all users have logged in from, via locations --show.
<<lessThis was inspired by a similar script discussed in the Perl For System Administration book from O Reilly.
By default this script will display all the users who have logged into your box from more than three distinct locations - this may be tweaked via the --count=N argument.
Alternatively you may ask for a report on all the hosts all users have logged in from, via locations --show.
Download (0.012MB)
Added: 2007-08-21 License: GPL (GNU General Public License) Price:
797 downloads
Fast Icon Users for Linux -
User icons with functions like: add, chat, edit, offline, remove, send, upload more>> Description:
11 icons of users.
Content:
User icons with functions like: add, chat, edit, offline, remove, send, upload, user, user group, video chat, voice chat<<less
Download (313KB)
Added: 2009-04-04 License: Freeware Price:
211 downloads
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
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
Copernicus for Linux 2.0
Copernicus is a username and password remembering program for Linux more>> Copernicus is a username and password remembering program that enables you to store all your various internet login details in one convenient location. Rest assured, it is totally free from spyware and adware which tend to haunt this type of program. Apart from its ease of use, other benefits of Copernicus include the fact that it doesnt cost you a cent, is open source, will work on most modern computing platforms such as Linux, Mac OS X and Windows, and is available in more than ten different languages.
Features
Copernicus is extremely easy to use - as you can see from the screenshots listed on this page, all of your sites are listed on the left hand side. If you click on one of those sites - the associated login details (username, password and any other information you require) are displayed on the left. Due to the fact many people have multiple logins for a single site - you can even have several logins associated with the one site and can browse the other ones by clicking on the login drop down box, or clicking the shortcut for the next login (denoted by the > symbol).
Copernicus is well suited to a multi-user computer as each user can have their own copernicus file where they store their logins.
Like all Tank Software programs, Copernicus strives to be highly customisable. You can change the language that Copernicus uses to one of the many included translations (there are over ten, including French, German, Greek, Japanese, Russian and Spanish). If you dont like the Look & Feel (a.k.a the GUI theme), you can choose between the Kunststoff Java Metal theme (default, example at top), your System default theme (Windows, example at bottom) the standard Java theme or even a custom Java Look & Feel.
As stated above, Copernicus is accessible by most computer users supporting many different languages and operating systems.<<less
Download (428KB)
Added: 2009-04-20 License: Freeware Price: Free
186 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
Multi-Protocol Remote Login 0.3.0
Multi-Protocol Remote Login provides a middleware allowing SSH, telnet, and local logins from the login: prompt. more>>
Multi-Protocol Remote Login provides a middleware allowing SSH, telnet, and local logins from the login: prompt.
MPRL is a middleware application between a *getty program and SSH, telnet, and other such remote-login protocols. It allows a user at a Linux terminal to log into other systems without needing a valid local user-id. It currently supports telnet, ssh, and /bin/login.
It syntax follows the [protocol:]user[@host][:port] fashion.
These are valid logins:
- buanzo - Normal local login: /bin/login gets called.
- buanzo@linux.org.ar - SSH protocol by default: /usr/bin/ssh gets called
- ssh:buanzo@webserver.algo.net
<<lessMPRL is a middleware application between a *getty program and SSH, telnet, and other such remote-login protocols. It allows a user at a Linux terminal to log into other systems without needing a valid local user-id. It currently supports telnet, ssh, and /bin/login.
It syntax follows the [protocol:]user[@host][:port] fashion.
These are valid logins:
- buanzo - Normal local login: /bin/login gets called.
- buanzo@linux.org.ar - SSH protocol by default: /usr/bin/ssh gets called
- ssh:buanzo@webserver.algo.net
Download (0.022MB)
Added: 2007-02-28 License: GPL (GNU General Public License) Price:
971 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
Cornfed SIP User Agent 1.1.4
Cornfed SIP User Agent is a SIP Softphone. more>>
Cornfed SIP User Agent is a Session Initiation Protocol (SIP) based softphone for your IBM-compatible Personal Computer running the Linux operating system.
The Cornfed SIP User Agent allows you to make Internet phone calls using an Advanced Linux Sound Architecture (ALSA) or Open Sound System (OSS) sound card with speakers and microphone as your telephone handset.
Main features:
- Supports SIP (RFC 3261), SDP (RFC 2327), and RTP (RFCs 3550 and 3551)
- Automated detection of Residential Gateways using Network Address Translation (NAT)
- Supports Digest authentications for registrations and outbound INVITEs
- Support for loose proxy routing using Record-Route and Route headers
- Handles forking of outbound INVITEs by proxies
- Supports re-INVITEs for changes to media transport
- Supports G.711 mu-Law and a-Law voice codecs
- Supports RFC 2833 DTMF tone generation
- Supports SIP compact header forms
- Gnome GUI and CLI clients
- Multi-threaded implementation
The Cornfed SIP User Agent is provided free of charge for personal use for users of the Linux operating system. The program is provided as a binary distribution only. The Cornfed SIP User Agent is specifically designed with embedded and mobile wireless devices in mind.
Development is under way to bring this client to other platforms. If you are interested in licensing this technology for your commercial application, please contact Cornfed Systems at 410-404-8790.
Enhancements:
- Minor bug fixes.
- Changed readline functionality to used raw input rather than cooked mode.
- Fixed bugs with display of status messages that caused client to hang.
- Disabled removal of registration on client exit.
<<lessThe Cornfed SIP User Agent allows you to make Internet phone calls using an Advanced Linux Sound Architecture (ALSA) or Open Sound System (OSS) sound card with speakers and microphone as your telephone handset.
Main features:
- Supports SIP (RFC 3261), SDP (RFC 2327), and RTP (RFCs 3550 and 3551)
- Automated detection of Residential Gateways using Network Address Translation (NAT)
- Supports Digest authentications for registrations and outbound INVITEs
- Support for loose proxy routing using Record-Route and Route headers
- Handles forking of outbound INVITEs by proxies
- Supports re-INVITEs for changes to media transport
- Supports G.711 mu-Law and a-Law voice codecs
- Supports RFC 2833 DTMF tone generation
- Supports SIP compact header forms
- Gnome GUI and CLI clients
- Multi-threaded implementation
The Cornfed SIP User Agent is provided free of charge for personal use for users of the Linux operating system. The program is provided as a binary distribution only. The Cornfed SIP User Agent is specifically designed with embedded and mobile wireless devices in mind.
Development is under way to bring this client to other platforms. If you are interested in licensing this technology for your commercial application, please contact Cornfed Systems at 410-404-8790.
Enhancements:
- Minor bug fixes.
- Changed readline functionality to used raw input rather than cooked mode.
- Fixed bugs with display of status messages that caused client to hang.
- Disabled removal of registration on client exit.
Download (0.78MB)
Added: 2007-07-03 License: Free for non-commercial use Price:
529 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
Resolver User Layer Interface 0.36
RULI stands for Resolver User Layer Interface. more>>
RULI stands for Resolver User Layer Interface. Its a library built on top of an asynchronous DNS stub resolver. RULI provides an easy-to-use interface for querying DNS SRV resource records. The goal is to promote wide deployment of SRV-cognizant software. RULI aims to fully support SRV-related standards. There are bindings for PHP, Perl, Guile/Scheme, Java, and Lua. IPv6 is supported.
Now you can understand the benefits of SRV records and please see how RULI can help you.
SRV records are more complex than A records
Handling DNS SRV is not as simple as to deal with ordinary address records. When one performs a query for A records by calling gethostbyname(), he gets a list of addresses which should be contacted in the same order as they were received. For SRV records, there is an additional logic that must be applied to the records, based on their weight and priority, to discover the correct sequence for contacting them.
RULI can handle SRV records for you
The SRV logic is described in RFC 2782. Those who intend to use SRV benefits in their application are expected to implement that exact behavior. RULI can help here: it automatically performs all the SRV logic for you.
Keep focus on your application logic
Application developers probably want to spend time on their business logic; not dealing with the details of the DNS protocol or implementing the SRV specification.
RULI is a tested framework designed to properly fetch SRV records. It saves you time and head aches.
RULI is free as in free beer and in free speech
<<lessNow you can understand the benefits of SRV records and please see how RULI can help you.
SRV records are more complex than A records
Handling DNS SRV is not as simple as to deal with ordinary address records. When one performs a query for A records by calling gethostbyname(), he gets a list of addresses which should be contacted in the same order as they were received. For SRV records, there is an additional logic that must be applied to the records, based on their weight and priority, to discover the correct sequence for contacting them.
RULI can handle SRV records for you
The SRV logic is described in RFC 2782. Those who intend to use SRV benefits in their application are expected to implement that exact behavior. RULI can help here: it automatically performs all the SRV logic for you.
Keep focus on your application logic
Application developers probably want to spend time on their business logic; not dealing with the details of the DNS protocol or implementing the SRV specification.
RULI is a tested framework designed to properly fetch SRV records. It saves you time and head aches.
RULI is free as in free beer and in free speech
Download (0.12MB)
Added: 2006-07-15 License: GPL (GNU General Public License) Price:
1197 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 logins 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
