Free to provide access software for linux

mod_access_referer is a module for the Apache HTTP Server that provides access control based on "Referer" HTTP header content.

Why is mod_access_referer useful?
Basically, it allow or deny the access based on what page is shown in the Web browser, which means that if you publish a document (picture, chart or other) in your site, the people will have to visit your Web site to access it, and no one will be able to link just the document.

Motivation:

There are many organizations that publish valuable files (pictures, charts, and other documents) in their Web sites. Those organizations want to make public those files, but at the same time they want the people having visiting their Web sites in order to get those files (example, in order to get revenue from sell banners which are shown at the Web site).

But, there are situations where the files are linked from other Web sites, other than the organization owns. In such situations, the organization is loosing twice: one because the people dont visit the organizations Web site to get the files, and another because the organization still pay the necessary bandwidth to get the files.

Most browsers today send the "Referer" HTTP header in each request that comes from another Web page. This can be used to track from where the resources are linked, but it can be used to allow or deny the access to such resources if the "Referer" is not a page from the organizations Web site.

mod_access_referer is an Apache module that understand the "Referer" HTTP header, and grant or deny access based on the Web page that refered the file.
The "Referer" HTTP header is sent by the browser to the server, and it contains the URL of the resource from where the URL of the asked resource was obtained. The document "Hypertext Transfer Protocol -- HTTP/1.1" RFC 2616 gives the following explanation:

"The Referer[sic] request-header field allows the client to specify, for the servers benefit, the address (URI) of the resource from which the Request-URI was obtained (the "referrer", although the header field is misspelled.) The Referer request-header allows a server to generate lists of back-links to resources for interest, logging, optimized caching, etc. It also allows obsolete or mistyped links to be traced for maintenance. The Referer field MUST NOT be sent if the Request-URI was obtained from a source that does not have its own URI, such as input from the user keyboard."

The MDB Tools project is a effort to document the MDB file format used in Microsofts Access database package, and to provide a set of tools and applications to make that data available on other platforms.

Specifically, MDB Tools includes programs to export schema and data to other databases such as MySQL, Oracle, Sybase, PostgreSQL, and others.

Also, included is a SQL engine for performing simple SQL queries. The 0.5 release includes an updated GUI interface (screenshot is available here). A sparse but functional ODBC driver is included as well.

MDB Tools currently has read-only support for Access 97 (Jet 3) and Access 2000/2002 (Jet 4) formats. Access 2000 support is a recent addition and may not be as complete as Jet 3 support.

Write support is currently being worked on and the first cut is expected to be included in the 0.6 release.

The QDS library allows Qt applications to access features provided in common desktop APIs in a portable way, without requiring dependencies on any desktop platform library.
This is especially useful for applications targeting the Unix desktops, because Qt/X11 is very generic and only provides features it can implement on all sub platforms. All library code is licenced under 2-clause BSD licence.
Service implementations are loaded from plugins which link to the respective desktop libraries. The plugin to use can be specified on the applications commandline, in the QDS configuration file or QDS can try to autodetect the currently running platform.
Enhancements:
- Autodetection to use GNOME plugin in case GNOME_DESKTOP_SESSION_ID is set
- Replaced the primitive example application with a simple but network aware text editor application
- Support for wildcards in mailcap entries

WebService::Google::Sets is a Perl access to Google Labs Sets site.

SYNOPSIS

use WebService::Google::Sets;

my @os_list = qw(Linux Windows Solaris);
my $expanded_os_list = get_gset(@os_list);

# check something came back
die "No results returned from server" unless $expanded_os_list;

foreach my $element (@$expanded_os_list) {
print $element, "n";
}

WebService::Google::Sets provides function based access to the Sets service hosted at Google Labs.

The Sets service attempts to expand the values you provide. The example provided in the SYNOPSIS would return an array that included "Windows NT", "HPUX" and "AIX" as values in addition to those supplied.

DACS is an open source identity management and access control system for web services. The web services can be virtually any static or computational resources provided through HTTP.
Main features:
- a flexible and powerful role-based access control system;
- a set of feature-rich authentication methods;
- an Apache 2.0.X module and suite of CGI programs;
- a federated identity management system (single sign-on);
- oriented towards (but not limited to) controlling access to web service requests made using standard web browsers;
- a collection of web services that can provide access control and identity management functionality to your middleware;
- a C/C++ toolkit for building new authentication and access control functionality into programs, whether web-based or not;
- for Unix-type platforms (currently), such as Linux, FreeBSD, and Solaris; and has
- an open, lightweight design and portable implementation.
DACS can help you to manage access to web resources in many situations, whether you have just one web server, several web servers at one site, or many web servers spread across the Internet.
You may find it to be useful simply as a universal authentication mechanism for a single Apache server or as a full-fledged, single sign-on multi-server identity management and access control system.
DACS may be of interest to developers more interested in authentication functionality than access control. DACS identities can be integrated with HTTP-based clients, whether interactive or not, and non-web based client/server applications.
Designed and implemented by DSS, development of DACS was initiated in May, 2001. DACS is a key component of Canadas National Forest Information System (NFIS).
Enhancements:
- This is primarily a bug fix and minor enhancements release. DACS is security software - we urge all users to upgrade to the latest release.

MobileFS is a virtual file system builded on FUSE to provide access to any OBEX-compliant mobile device.
The project supports all Siemens mobile L55 series, including:
- A55
- A56
- A56i
- A60
- C55
- C56
- 2128
- CT56
- C60
- C61
- C62
- CF62
- M46
- M50
- MT50
- 3118
To install, run:
cp src/mobfs /sbin/mount.mobfs

Hivetools software is organized into a low-level library (lib), a mid-level library (hivetools) and user programs (bin). The low-level library provides access to raw hive files. Its interface attempts to approximate that of the win32 registry API.
The mid-level library facilitates use of the low-level library. It provides a POSIX-like API as well as functions that operate on data stored within the registry (such as SAM data). The programs leverage both the mid and low-level libraries. They allow users to perform actions upon the registry.
Programs (bin)
- regmod - insert and extract .reg (Regedit style) files
- hiveshell - what has become of the chntpw interface. Some of the chntpw functionality is still missing from hiveshell at this time.
- sam - provides access to Security Accounts Manager data
Mid-level Library (hivetools)
The mid-level library is found in the hivetools directory (which may be renamed in the near future). It currently provides the following:
- nstdreg: provides registry access through a more POSIX-like interface. Provides functions such as
- ns_open(char*) open a registry key such as "HKEY_LOCAL_MACHINE/software/whatever"
- ns_opendir(char*)
- ns_readdir()
- ns_rewinddir()
- ns_mkdir()
- ns_unlink()
- ns_exists()
- etc, etc...
- sam: provides access to the SAM database
- retrieve user list
- decode user V,F structures
- decode SAM F structure
- password crypto functions
Low-level library (lib)
The low-level library attempts to emulate (currently poorly) the windows registry API. It provides functions such as:
- long rlRegOpenHiveFile(rl_hkey *result, const char *fname, const char *keypath, int mode );
- long rlRegOpenKeyEx(rl_hkey hkey, const char *skname, ulong options, REGSAM, rl_hkey *result);
- long rlRegQueryValueEx(rl_hkey key, const char *vname, unsigned long *type,
- long rlRegEnumKeyEx(rl_hkey, unsigned long index, char *name, unsigned long *len, char *cname,
- long rlRegEnumValue(rl_hkey key, unsigned long index, char *vname, unsigned
- long rlRegSetValueEx( rl_hkey key, const char *vname, ulong reserved, ulong type, const char* buf, ulong blen);
- long rlRegCreateKeyEx(rl_hkey hkey, const char *skname, const char *r_class, unsigned long options, REGSAM desired,
- long rlRegQueryInfoKey()
- long rlRegQueryMultipleValues()
- long rlRegCloseKey(rl_hkey key)
- long rlRegFlushKey(rl_hkey key)
- long rlRegDeleteKey(rl_hkey key, const char *skname)
- long rlRegDeleteValue(rl_hkey key, const char *vname)