mod auth pipe 1.0
mod_auth_pipe 1.0
mod-auth-pipe is a module of authentication written for Apache 1 (it hasnt been tested with Apache 2, but it may work). more>>
Actually, this module is just mod-auth-shadow with a few modifications in order to accept any program as a pipe, letting this one validate both users andr groups.
mod_auth_pipe contents the module itself and an example pipe.
mod-auth-pipe can be configured independantly for whole server, for any VirtualHost or just per Location/Directory. It has very few configuration variables and its format is very simple. In order to configure apache to authenticate, for example, access to the administrative interface of oscommerce you can type this on your httpd.conf:
< Directory /var/www/oscommerce/catalog/admin >
AuthType Basic
AuthName osCommerce admin site
AuthPipe on
AuthPipeProgram /usr/local/bin/auth-pipe
require group oscommerce-admins
< /Location >
This way, and with a well-made auth-pipe program you can be sure that only those within the group oscommerce-admins could enter that section of your web.
mod_auth_udp 1.0
mod_auth_udp is a forwarding auth-requests to an external Server with udp-packets Apache module. more>>
The first implementation of the server is written in C and queries a PostgreSQL database, but I have designed it in a way, that there is only one file, that interacts with PostgreSQL. So you can think of this server as a template for building your own.
mod_auth_token 1.0.1
mod_auth_token module uses token based authentication to secure downloads and prevent deep-linking. more>>
Have your PHP script or servlet generate the to authenticate the download. Apache can then treat the download request like a normal file transfer without having to pipe the file through a script in order to add authentication.
You can find downloads, daily snapshots and support information at http://www.synd.info/
Usage:
The token is an hex-encoded MD5 hash of the secret password, relative file path and the timestamp. It is encoded onto the URI as:
< uri-prefix >< token >/< timestamp-in-hex >< rel-path >
For example
/protected/dee0ed6174a894113d5e8f6c98f0e92b/43eaf9c5/path/to/file.txt
where the token is generated as
md5("secret" + "/path/to/file.txt" + dechex(time_now()))
with the following configuration in httpd.conf
< Location /protected/ >
AuthTokenSecret "secret"
AuthTokenPrefix /protected/
AuthTokenTimeout 60
< /Location >
The actual file would should be located in
/protected/path/to/file.txt
Auth MemCookie 1.0
Auth MemCookie is an Apache v2 authentification and authorization modules are based on cookie authentification mecanism. more>>
The module dont make authentification by it self, but verify if authentification "the cookie" are valid for each url protected by the module. The module validate also if the "authentificated user" have authorisation to acces url.
Authentification are made externaly by an authentification form page and all authentification information nessary to the module a stored in memcached indentified by the cookie value "authentification session id" by this login page.
How it Works
Phase 1 : The login Form
Authentification are made by a login formular page.
This login page must authenticate the user with any authenticate source (ldap, /etc/password, file, database....) accessible to langage of the page (php, perl, java... an ldap login page sample in php are in samples directory).
Then must set cookie that contain only a key the "authentification unique id" of the "authentification session".
The login page must store authorisation and user information of the authenticated user in memcached identified by the cookie key "authentification unique id".
The login page can be developted in any langage you want, but must be capable to use memcached (they must have memcache client api for us)
Phase 2 : The Apache v2 Module
After the user are logged, the apache 2 module check on each protected page by apache ACL the presence of the "cookie".
if the "cookie" exist, try to get session in memcached with the "cookie" value if not found return "HTTP_UNAUTHORIZED" page.
if session exist in memcached verify if acl match user session information if not match return "HTTP_FORBIDDEN" page.
Mod-Cache 1.4
Mod-Cache is a cache(reverse-proxy) accelerator plugin for lighttpd, which works like Squid with similar configuration. more>>
Mod-Cache has following advantages over Squid:
- Simpler. Mod-Cache just sets proper flags between lighttpd request handling stages. Request is handled by mod_staticfile or mod_compress or other modules.
- More Robust. Mod-Cache uses disk file instead of memory as cache. Without use of memory, mod_cache is far away from memory leaks and memory exhaustion.
- Faster. Lighttpd uses Sendfile syscall to service disk file. Sendfile syscall, which writes file to network interface directly, has the same effecience as Writev syscall which writes memory buffers to network interface.
- More Powerful. Mod-Cache can works with other lighttpd plugins(except mod_deflate). For examples, you can use mod_compress to compress cached files on-fly; or you can use mod_access/mod_trigger_b4_dl to do anti-hot-link; or you can use mod_flv_streaming to do native flv file streaming.
Enhancements:
- lighttpd 1.5 was upgraded to r1811.
- The status page for mod_status was added.
- cache.ignore-hostname was added.
- A bug for checking the cachehd file was fixed.
mod_auth_shadow 1.6
mod_auth_shadow is an Apache module for authentication using /etc/shadow. more>>
When performing this task one encounters one fundamental difficulty: The /etc/shadow file is supposed to be read/writeable only by root. However, the webserver is supposed to run under a non-root user, such as "nobody".
mod_auth_shadow addresses this difficulty by opening a pipe to an suid root program, validate, which does the actual validation. When there is a failure, validate writes an error message to the system log, and waits three seconds before exiting.
Pipe-Sem 1.0
This is a pipe based semaphore implementation for developing ASYNC applications. more>>
Pipe-Sem 1.0 is a good utility which might help you a lot in developing ASYNC applications. Many synchronization primitives are available for Unix systems, but any of them expose a pollable interface to the user. In these cases, if the caller execute a down operation on a blocking semaphore, the application will sleep and whole ASYNC loop will starve because of the wait.
To cope with this problem in ASYNC software, the publisher developed a pipe based semaphore implementation, called Pipe-Sem. The implementation is trivially simple and it uses the pipe internal mechanisms to expose a pollable wait interface.
Besides the standard semaphore operations, the function psem_down_fd() can be used to retrieve a files descriptor that can be dropped inside a Unix pollable API like select(2), poll(2) or epoll(2). The caller will have to wait for input events (POLLIN), and when receiving the event itself, the caller should invoke the psem_try_down() function to try to acquire the semaphore.
Please note that receiving an event from the pollable interface, does not mean that we acquired to semaphore, and the function psem_try_down() will have to be called (and tested for zero return code) to correctly complete the down operation.
<<lessOpenVPN Auth Passwd 1.1
OpenVPN Auth Passwd is a plugin that authenticates OpenVPN users using the local passwd or shadow files. more>>
OpenVPN Auth Passwds authentication method must be defined in the Makefile prior to the compilation of the plugin.
On shadowed systems it uses the functions provided in the shadow suite and, on other systems, the getpwnam(3) function to verify the username/password.
SYNOPSIS
The openvpn-auth-passwd module implements username/password authentication via the passwd files and, in the systems with shadow support, we use it. It is provided for systems that dont have PAM.
This module uses a split privilege execution model, the same used in the auth-pam and down-root plugins. That is, even if you drop the openvpn daemon privileges using the user, group, or chroot directives, the plugin still work.
BUILD
To build openvpn-auth-passwd on systems that use shadow, you will need to have the shadow suite and its devel headers installed.
On GNU systems build with the "make" command. In other systems you should install the GNU make, if you dont have it, and type "gmake". The module will be named openvpn-auth-passwd.so
USAGE
To use this plugin module, add to your OpenVPN config file:
plugin openvpn-auth-passwd.so
Run OpenVPN with --verb 7 or higher to get debugging output from this plugin.
CAVEATS
This module is supposed to work on any *nix system but, more testing should be done. Right now it works in the Linux and OpenBSD.
There is no portable way to check if you are using the shadow suite or not. And, as we are not using autoconf to do this, you must manually set the USE_SHADOW directive in the Makefile. We assume by default that you are using it (the majority of linux distributions and sun). If you arent (the majority of *bsd systems and others),
you should set it to 0.
Enhancements:
- Added a new funtion to check if the user belong to a given group or not.
mod-apache-snmp 1.03
Apache SNMP Module allows you to monitor different configuration and status values of the Apache Web server using SNMP. more>>
Enhancements:
- Bugfixes, the inclusion of MRTG scripts, and changes to make the module work on the IBM HTTP Server.
mod-vhost-ldap 1.0
mod-vhost-ldap is an Apache 2.x module for storing and configuring virtual hosts from LDAP. more>>
Its built on top of mod_ldap, so it uses its caching capabilities and can be used with a threaded Apache httpd.
mod_auth_shadow2 2.2
mod_auth_shadow is an Apache module for authentication using /etc/shadow. more>>
When performing this task one encounters one fundamental difficulty: The /etc/shadow file is supposed to be read/writeable only by root. However, the webserver is supposed to run under a non-root user, such as "nobody".
mod_auth_shadow addresses this difficulty by opening a pipe to an suid root program, validate, which does the actual validation. When there is a failure, validate writes an error message to the system log, and waits three seconds before exiting.
smixer 1.0.4
smixer is a command-line and scriptable program to control and display the mixer volume levels on a sound card in linux. more>>
Distrubution of smixer is under the GNU GPL. See the "COPYING" and/or smixer.c file for more information.
Usage is explained very good in the man page.
smixer may be invoked with the following command-line options:
-a When printing current settings include all devices.
-p Print out the current mixer settings, then exit.
-f file Process commands from file, then exit.
[no options] Process commands from stdin (interactive or from a pipe), then exit.
Tmpf 1.0
Tmpf is tiny script (written in Ruby) to write standard output to a temporary file. more>>
The project is useful when you want to pipe output to a program that only accepts files, not standard input. Example: cat myfile.ps | tmpf gv (equivalent to: gv myfile.ps). Despite the incredible simplicity of this script, there is nothing quite like it provided among the standard Unix tools.
Simple UDP proxy/pipe 0.3
Simple UDP proxy/pipe is an advanced UDP proxy/datapipe/packets forwarder and modifier with multiple functions. more>>
Multiple clients allowed (you can connect many clients you want to this proxy), creation of ACP files (tcpdump capture files, just like a sniffer), packets forwarding (chat style, each packet is forwarded to all the other clients and server connected), packets injection (the tool opens a specific UDP port where you can send your customized packets which will be sent to the server), hexadecimal visualization and plugins support for the modification and visualization of the packets with some example plugins already included (Zdaemon huffman, Doom huffman, Half-life decoding and one for the replacement of the text strings).
Plugins (which work on both Windows and Linux) are very basic to create and use, just take a look at example_sudp.c for more informations.
Pipe Viewer 1.0.1
Pipe Viewer is a pipeline data transfer meter. more>>
It can be inserted into any normal pipeline between two processes to give a visual indication of how quickly data is passing through, how long it has taken, how near to completion it is, and an estimate of how long it will be until completion.
pv is now considered to be stable code: it appears to work reliably on systems it has been tested on.