Free sethandler software for linux

Net::CyanChat is a Perl interface for connecting to Cyan Worlds chat room.

SYNOPSIS

use Net::CyanChat;

my $cyan = new Net::CyanChat (
host => cho.cyan.com, # default
port => 1812, # main port--1813 is for testing
proto => 1, # use protocol 1.0
refresh => 60, # ping rate (default)
);

# Set up handlers.
$cyan->setHandler (foo => &bar);

# Connect
$cyan->start();

Net::CyanChat is a Perl module for object-oriented connections to Cyan Worlds, Inc.s chat room.

mod_xmltime produces an XML timestamp for +1200 to -1200 UTC Zones. mod_xmltime creates an XML Date/Time graph.
Installation:
- Verify that you have a late version of libxml2.
- Verify that apxs is on your path (it should have installed with your Apache installation).
- Download mod_xmltime.tar.gz.
- Un-tar the file (i.e. tar -zxf mod_xmltime.tar.gz )
- enter the mod_xmltime directory (i.e. cd path/to/mod_xmltime)
- If your lib and include directories are NOT in /usr/local, type make WITH_PREFIX=/PATH/TO/PREFIX all otherwise type make all
- Switch user (su) to a user with permission to write into /path/to/apache/installation (i.e. root)
- Type make install
- Verify that the following items are in your httpd.conf file:
- LoadModule xobjex_module libexec/apache/mod_xmltime.so
- AddModule mod_xmltime.c
< IfModule mod_xmltime.c >
< FilesMatch "timestamp.xml" >
SetHandler xmltime-handler
< /FilesMatch >
< /IfModule >
- Restart your Apache httpd or make reload, instead.

Apache2::AuthCookieDBI is an AuthCookie module backed by a DBI database.

SYNOPSIS

# In httpd.conf or .htaccess

PerlModule Apache2::AuthCookieDBI
PerlSetVar WhatEverPath /
PerlSetVar WhatEverLoginScript /login.pl

# Optional, to share tickets between servers.
PerlSetVar WhatEverDomain .domain.com

# These must be set
PerlSetVar WhatEverDBI_DSN "DBI:mysql:database=test"
PerlSetVar WhatEverDBI_SecretKey "489e5eaad8b3208f9ad8792ef4afca73598ae666b0206a9c92ac877e73ce835c"

# These are optional, the module sets sensible defaults.
PerlSetVar WhatEverDBI_User "nobody"
PerlSetVar WhatEverDBI_Password "password"
PerlSetVar WhatEverDBI_UsersTable "users"
PerlSetVar WhatEverDBI_UserField "user"
PerlSetVar WhatEverDBI_PasswordField "password"
PerlSetVar WhatEverDBI_CryptType "none"
PerlSetVar WhatEverDBI_GroupsTable "groups"
PerlSetVar WhatEverDBI_GroupField "grp"
PerlSetVar WhatEverDBI_GroupUserField "user"
PerlSetVar WhatEverDBI_EncryptionType "none"
PerlSetVar WhatEverDBI_SessionLifetime 00-24-00-00

# Protected by AuthCookieDBI.
< Directory /www/domain.com/authcookiedbi >
AuthType Apache2::AuthCookieDBI
AuthName WhatEver
PerlAuthenHandler Apache2::AuthCookieDBI->authenticate
PerlAuthzHandler Apache2::AuthCookieDBI->authorize
require valid-user
# or you can require users:
require user jacob
# You can optionally require groups.
require group system
< /Directory >

# Login location.
< Files LOGIN >
AuthType Apache2::AuthCookieDBI
AuthName WhatEver
SetHandler perl-script
PerlHandler Apache2::AuthCookieDBI->login
< /Files >

This module is an authentication handler that uses the basic mechanism provided by Apache2::AuthCookie with a DBI database for ticket-based protection. It is based on two tokens being provided, a username and password, which can be any strings (there are no illegal characters for either). The username is used to set the remote user as if Basic Authentication was used.

On an attempt to access a protected location without a valid cookie being provided, the module prints an HTML login form (produced by a CGI or any other handler; this can be a static file if you want to always send people to the same entry page when they log in). This login form has fields for username and password. On submitting it, the username and password are looked up in the DBI database. The supplied password is checked against the password in the database; the password in the database can be plaintext, or a crypt() or md5_hex() checksum of the password. If this succeeds, the user is issued a ticket. This ticket contains the username, an issue time, an expire time, and an MD5 checksum of those and a secret key for the server. It can optionally be encrypted before returning it to the client in the cookie; encryption is only useful for preventing the client from seeing the expire time. If you wish to protect passwords in transport, use an SSL-encrypted connection. The ticket is given in a cookie that the browser stores.

After a login the user is redirected to the location they originally wished to view (or to a fixed page if the login "script" was really a static file).
On this access and any subsequent attempt to access a protected document, the browser returns the ticket to the server. The server unencrypts it if encrypted tickets are enabled, then extracts the username, issue time, expire time and checksum. A new checksum is calculated of the username, issue time, expire time and the secret key again; if it agrees with the checksum that the client supplied, we know that the data has not been tampered with. We next check that the expire time has not passed. If not, the ticket is still good, so we set the username.

Authorization checks then check that any "require valid-user" or "require user jacob" settings are passed. Finally, if a "require group foo" directive was given, the module will look up the username in a groups database and check that the user is a member of one of the groups listed. If all these checks pass, the document requested is displayed.
If a ticket has expired or is otherwise invalid it is cleared in the browser and the login form is shown again.

Apache::ePerl is a fast emulated Embedded Perl (ePerl) facility.

SYNOPSIS

# Apaches httpd.conf file
# mandatory: activation of Apache::ePerl
PerlModule Apache::ePerl
< Files ~ "/root/of/webmaster/area/.+.iphtml$" >
Options +ExecCGI
SetHandler perl-script
PerlHandler Apache::ePerl
< /Files >
# optional: configuration of Apache::ePerl
< Perl >
$Apache::ePerl::Config->{BeginDelimiter} = $Apache::ePerl::Config->{EndDelimiter} = !>;
$Apache::ePerl::Config->{CaseDelimiters} = 0;
$Apache::ePerl::Config->{ConvertEntities} = 1;
< /Perl >
# optional: activation of Apache::Status for Apache::ePerl
< Location /perl-status >
Options +ExecCGI
SetHandler perl-script
PerlHandler Apache::Status
< /Location >

This packages provides a handler function for Apache/mod_perl which can be used to emulate the stand-alone Server-Side-Scripting-Language ePerl (see eperl(3) for more details) in a very fast way. This is not a real 100% replacement for nph-eperl because of reduced functionality under some special cases, principal runtime restrictions and speedup decisions. For instance this variant does not (and cannot) provide the SetUID feature of ePerl nor does it check for allowed filename extensions (speedup!), etc. Instead it uses further features like object caching which ePerl does not use.

But the accepted bristled source file format is exactly the same as with the regular ePerl facility, because Apache::ePerl uses the Parse::ePerl package which provides the original ePerl parser and translator. So, any valid ePerl which works under nph-eperl can also be used under Apache::ePerl.

The intent is to use this special variant of ePerl for scripts which are directly under control of the webmaster. In this situation no real security problems exists for him, because all risk is at his own hands. For the average user you should not use Apache::ePerl. Instead additionally install the regular stand-alone ePerl facility (nph-eperl) for those users.

So, the advantage of Apache::ePerl against the regular nph-eperl is better performance and nothing else. Actually scripts executed under Apache::ePerl are at least twice as fast as under nph-eperl. The reason its not that ePerl itself is faster. The reason is the runtime in-core environment of Apache/mod_perl which does not have any forking overhead.

Alarm::Concurrent is a Perl module that allows multiple, concurrent alarms.

This module is an attempt to enhance Perls built-in alarm/$SIG{ALRM} functionality.

This function, and its associated signal handler, allow you to arrange for your program to receive a SIGALRM signal, which you can then catch and deal with appropriately.

Unfortunately, due to the nature of the design of these signals (at the OS level), you can only have one alarm and handler active at any given time. Thats where this module comes in.

This module allows you to define multiple alarms, each with an associated handler. These alarms are sequenced (in a queue) but concurrent, which means that their order is preserved but they always go off as their set time expires, regardless of the state of the other alarms. (If youd like to have the alarms only go off in the order you set them, see Alarm::Queued.)

To set an alarm, call the setalarm() function with the set time of the alarm and a reference to the subroutine to be called when the alarm goes off. You can then go on with your program and the alarm will be called after the set time has passed.

It is also possible to set an alarm that does not have a handler associated with it using Alarm::Concurrent::alarm(). (This function can also be imported into your namespace, in which case it will replace Perls built-in alarm for your package only.)

If an alarm that does not have a handler associated with it goes off, the default handler, pointed to by $Alarm::Concurrent::DEFAULT_HANLDER, is called. You can change the default handler by assigning to this variable.

The default $Alarm::Concurrent::DEFAULT_HANDLER simply dies with the message "Alarm clock!n".

IMPORT/EXPORT

No methods are exported by default but you can import any of the functions in the FUNCTIONS section.

You can also import the special tag :ALL which will import all the functions in the FUNCTIONS section (except Alarm::Concurrent::restore()).

OVERRIDE

If you import the special tag :OVERRIDE, this module will override Perls built-in alarm function for every namespace and it will take over Perls magic %SIG variable, changing any attempts to read or write $SIG{ALRM} into calls to gethandler() and sethandler(), respectively (reading and writing to other keys in %SIG is unaffected).

This can be useful when you are calling code that tries to set its own alarm "the old fashioned way." It can also, however, be dangerous. Overriding alarm is documented and should be stable but taking over %SIG is more risky (see CAVEATS).

Note that if you do not override alarm and %SIG, any code you use that sets "legacy alarms" will disable all of your concurrent alarms. You can call Alarm::Concurrent::restore() to reinstall the Alarm::Concurrent handler. This function can not be imported.