Free client access software for linux

mod_access is an Apache module to access control based on client hostname or IP address.

The directives provided by mod_access are used in < Directory >, < Files >, and < Location > sections as well as .htaccess files to control access to particular parts of the server. Access can be controlled based on the client hostname, IP address, or other characteristics of the client request, as captured in environment variables.

The Allow and Deny directives are used to specify which clients are or are not allowed access to the server, while the Order directive sets the default access state, and configures how the Allow and Deny directives interact with each other.

Both host-based access restrictions and password-based authentication may be implemented simultaneously. In that case, the Satisfy directive is used to determine how the two sets of restrictions interact.

In general, access restriction directives apply to all access methods (GET, PUT, POST, etc). This is the desired behavior in most cases. However, it is possible to restrict some methods, while leaving other methods unrestricted, by enclosing the directives in a < Limit > section.

Oww Client is a graphical client program for One-Wire Weather (Oww) servers. Oww Client is based on GTK+, displaying lists of collected weather data from one or more servers.
Enhancements:
- Owwl was enhanced to include new sensor types (mainly for cryogenic readout).
- A status window was added.
- Reconnexion is now automatic, after the remote server drops it.

FUSE::Client is a Perl-FUSE client.

SYNOPSIS

use FUSE::Client;
$c = FUSE::Client->new({
Port=>35008,
Quiet=>1,
});

$c->connect();
$c->send("COMMAND","parameter");
$c->disconnect();

The FUSE::Client module will create a TCP FUSE client to test sending messages to a FUSE server.

The external interface to FUSE::Client is:

$c = FUSE::Client->new( [%options] );

The object constructor takes the following arguments in the options hash:

Quiet = 0|1

Whether to be quiet. Default is to report all events to STDOUT (not Quiet).

Port = n

The port for the client to connect to. Default is 1024.

$c->connect();

This method connects the client to the server.

$c->disconnect();

This method disconnects the client from the server.

$c->send( $command, $parameter );

Send a FUSE formatted command message to the server, with the specified parameter.

Avis client library is a Java API for clients accessing Elvin event routers, including the open source Avis event router and the commercial Mantara Elvin product.
Avis is an event router service compatible with the commercial Elvin implementation developed by Mantara Software. Avis provides a fast, general-purpose publish/subscribe message bus.
Elvin event routers alllow arbitrary messages, known as notifications, to be exchanged via a publish/subscribe model. Elvin clients subscribe to messages published by other clients using expressions that match messages by their content.
The content-based routing approach used in Elvin routers differs from many other message bus systems that operate by selecting messages published on pre-defined channels, and has the advantage of promoting a much higher level of decoupling between producers and consumers of events.
The name "Avis" derives from the French word avis, meaning advice or notification.
Enhancements:
- This release marks a stable baseline for the Java client API.
- The core set of features required for an Elvin client library are now implemented and stable, including subscription, notification, security, close event notification, liveness checking, and router connection option support.

PHP Client Sniffer is a PHP class file that allows one to quickly determine the clients browser and system information based on the HTTP_USER_AGENT string. The class can be used to generate browser specific html marks and other client side scripting.
Enhancements:
- add k-meleon support
- add camino support
- add mozilla firebird support
- add amiga support
- fixed issues with netscape and gecko browsers

Direct Access Provider Library in short DAPL is a transport-independent, platform-independent, high-performance API for using the remote direct memory access (RDMA) capabilities of modern interconnect technologies such as InfiniBand, the Virtual Interface Architecture, and iWARP.
This is the reference implementation of that specification by the DAT Collaborative who maintain the DAPL API.
Enhancements:
- Support was added for new IB verbs client register event.
- Some problems supporting create qp without recv cq handle or recv qp resources were fixed.
- Some timeout and long disconnect delay issues exposed during scalability tests were fixed.
- Minor build problems were fixed.
- Support for multiple IB devices was added to dat.conf to support IPoIB HA failover.
- Support for returning local and remote port information was added.
- The RPM spec file was cleaned up.
- Enviroment variables to configure connection management timers were added.

HTTunnel::Client is a client class for Apache::HTTunnel.

SYNOPSIS

my $hc = new HTTunnel::Client("http://localhost/httunnel") ;
$hc->connect(tcp, $some_host, $some_port) ;

$hc->print(some request) ;
my $some_response = $hc->read(1024) ;

$ch->close() ;

HTTunnel::Client is the client class to Apache::HTTunnel. It allows the creation of a network connection tunnelled through HTTP. All data sent and received during this connection will be transported inside normal HTTP requests.

HTTunnel::Client extends LWP::UserAgent, so all LWP::UserAgent methods are available through HTTunnel::Client.

CONSTRUCTORS

new ( URL, [ARGS] )

Creates an HTTunnel::Client object that will use URL to contact the Apache::HTTunnel server. ARGS are is passed directly to the LWP::UserAgent constructor.

METHODS

connect ( PROTO, HOST, PORT, [TIMEOUT] )

Asks the Apache::HTTunnel server to establish a connection of protocol PROTO to HOST:PORT. An exception is thrown if an error occurs.

Accepted values for PROTO are tcp and udp.

print ( DATA )

Asks the Apache::HTTunnel server to write DATA to the established remote connection. An exception is thrown if an error occurs.
DATA can be a scalar or a list, in which case the list items are concatenated together.

read ( LEN, [TIMEOUT], [LIFELINE], [LIFELINE_CUT_ACTION] )

Asks the Apache::HTTunnel server to read up to LEN bytes from the established remote connection. An exception is thrown if an error occurs.

When trying to read, HTTunnel::Client will establish an HTTP connection to the Apache::HTTunnel server asking that LEN bytes be read. If no data is available after TIMEOUT seconds (the default value is 15 seconds), the HTTP connection is closed by the server and the read method will establish a new one. This will go on until some data or EOF is returned.

Therefore read will return only when some (or no more) data is available to be read (like the regular read).

LIFELINE can be any valid filehandle from which one can read. If used, read will interrupt its connection loop and execute LIFELINE_CUT_ACTION when data (or EOF) is available to be read from LIFELINE. It will then return undef.
LIFELINE_CUT_ACTION wust be a CODE ref. The default value is

sub {die("lifeline cutn")}

These features can be used if you want fork and to start a process that does nothing but reads and returns the data via a pipe. You can then use a second pipe to make sure the reader process terminates when the master process terminates.

Here is an example:

my $lifeline = new IO::Pipe() ;
my $reader = new IO::Pipe() ;
my $pid = fork() ;
if ($pid){
$reader->reader() ;
$lifeline->writer() ;

# Read data from $reader...
}
else {
$reader->writer() ;
$reader->autoflush(1) ;
$lifeline->reader() ;

while (1){
my $data = $hc->read(1024, 15, $lifeline, sub {exit()}) ;
exit() unless defined($data) ;
print $reader $data ;
}
}
close ( )

Asks the Apache::HTTunnel server to close a previously established connection.
get_peer_info ( )

The get_peer_info method returns information about the remote connection. A string containing the IP address and port number, separated by a colon (:) is returned. This method can be useful with UDP connections to validate the sender of each packet.

request_callback ( REQUEST )

The request_callback method is a callback method that can be used to access the HTTP::Request object just before it is sent. The default implementation does nothing.

response_callback ( RESPONSE )

The response_callback method is a callback method that can be used to access the HTTP::Response object just after it is received. The default implementation does nothing.

GPM client library (libgpm) package is an stand-alone version of GPMs client library, used by many console applications for mouse access.
Despite the (now quite aged) GPM package it contains just the client part (no server), and provides a pkgconfig descriptor (libgpm.pc) for easy importing.
Enhancements:
- This release pulls in some outstanding patches from upstream and Gentoo. It adds a Gentoo ebuild file.