Free allows easy access software for linux

JavaSVN project is a pure Java Subversion client library. You would like to use JavaSVN when you need to access or modify Subversion repository from your Java application, be it a standalone program, plugin or web application.
Being a pure Java program, JavaSVN doesnt need any additional configuration or native binaries to work on any OS that runs Java. On this site you will also find instructions on how to make existing programs use JavaSVN instead of native javahl bindings.
Main features:
- No external binaries or libraries are needed to work with Subversion repository.
- JavaSVN supports http, https, svn and svn+ssh connection protocols.
- New: file protocol is supported in 1.1.0.beta2 version.
- Low level API allows effective direct Subversion repository access.
- JavaSVN is compatible with applications that already use native javahl bindings.

Wiaflos Accounting project is an attempt to create a multi-platform server-client based accounting system.
The goal is to have a central accounting engine which can either run on a dedicated server or on the same PC as the client interface. The accounting engine will provide a full SOAP API for easy writing of GUI/Web interfaces or tieing into inhouse systems. Seeing as the accounting engine is written in Perl and makes use of a database abstraction layer, the engine should run on nearly any operating system and use nearly any database system supported by Perl and the target OS.
We want this package to be of equal use to the one-man-show as a full accounting package running on a single PC aswell as to large multi-national corporate entities with dedicated accounting servers using the package as a fast stable accounting function, solution or full package.
Main features:
Platform independant
- Wiaflos Accountings core and engine is written in Perl. Perl is an interpreted programming language capable of running on many different platforms including Unix/Linux, Mac, Windows, BSD and many more.
Database independent
- Wiaflos Accountings database interface utilizes the Perl DBI module. This module allows Wiaflos Accounting to access multiple database types transparently, allowing you to utilize the database of your choice, be it MySQL, MSSQL, Oracle, Informix, Sybase or ODBC (or basically anything else).
Folding database transactions
- All modules use database transactions to ensure that if an error occurs everything is rolled back to a safe state. When different modules are integrated to provide functionality like invoicing and purchasing, there are sometimes quite a number of transactions involved which both update, insert and query data. The Wiaflos Accounting database engine automatically merges all transactions during a specific operation into one, this ensures a clean rollback should anything go wrong.
SOAP API (WebServices)
- The interface to Wiaflos Accounting is based on SOAP (Simple Object Access Protocol). The SOAP protocol is a critical communication protocol on the Internet due in large part to the fact that it has become native to so many development platforms, this allows Wiaflos Accounting the maximum benefit of integration and interpolation with other software packages. The SOAP API supports communication over HTTP and HTTPS and includes a full user-based access control system, allowing only certain users access to certain API functions.
Persistent sessions
- Not only does Wiaflos Accounting support SOAP, but it supports persistent SOAP sessions. Authentication is only required once, after that a session cookie is handed to the client application which can then be used in future function calls to authenticate.
Enhancements:
- This version includes support for statements and "balance brought forward" when requesting GL entries.
- Some bugfixes and feature enhancements were made.

Access Stats provides a script that enables you to keep track of activities on your web site.

Access Stats allows you to keep track of activities on your web site.

It extracts some statistic from a log file generated by log.pl.

These reports are generated by Access Stats:

- Visits by day
- Visits by hour
- Visits by week-day
- Referer
- Browser
- Operating System
- Countries
- Hostnames

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."

Twisted Conch project is an SSHv2 implementation written in Python. SSH is a protocol designed to allow remote access to shells and commands, but it is generic enough to allow everything from TCP forwarding to generic filesystem access.
Since conch is written in Python, it interfaces well with other Python projects, such as Imagination. Conch also includes a implementations of the telnet and vt102 protocols, as well as support for rudamentary line editing behaviors.
A new implementation of Twisteds Manhole application is also included, featuring server-side input history and interactive syntax coloring.
Conch is available under the MIT Free Software licence.
Enhancements:
- The in-memory terminal emulators "expect" functionality now supports timeouts.
- The SSH server and client are now approximately five times faster for bulk-data transfers.

cowdancer allows copy-on-write file access. You can copy a full tree using hard links, and cowdancer will create a new copy when you need to write to a file.
cowdancer is completely implemented in userland, and should run on most Linux filesystems.
Enhancements:
- This release supports spaces in filenames.

RearSite is a simple collaborative Web site manager. RearSite is an automated Web publishing tool allowing to control who is allowed to access the published documents and also to manage per directories collaboratives tools well adapted to distance learning (forums, chats, shareable calendars, or multimedia quizzes).

An administrator can create users accounts (user name, user passwd, and user home directory), users get logged in and then receive access to their documents.


RearSite is written in PERL (CGI.pm based) and use a FastCGI compliant HTTP server (like APACHE).

Using RearSite is quite simple : after login, the user has access to his home dir and is able to delete, rename, create and edit documents. RearSite is well adapted to install WWW directories previously cooked (using any editors). Its very easy to transfer and install archives (ZIP, tar or tar.gz by now), they are automatically unpacked.

Published documents are public (by default), access restriction may be done using user/password couples, DNS domains or LDAP filters.

The user interface is WWW forms like, so RearSite only needs (on the client side) a Java, JavaScript and frames compliant WWW browser (accepting cookies).

RearSite is now quite secured, the login process (developped in Java) use an MD5 encryption of the user password (combined with a one time key). So, people spying the network cannot use the keys they may have seen. After login, users receive a cookie associated with their computers IP numbers.

RearSite also allows the user to specify who can retrieve his documents by configuring access rights :

documents are public (the default).
documents are restricted to users coming from trusted domains.
documents are restricted to users coming from trusted domains or to HTTP authenticated users.
* documents are restricted to class of users existing in an LDAP directory. This kind of HTTP client authentication needs auth_ldap for Apache (See restricted access by users classes).

Since 1.1, if the administrator wants it, the user is able to use templates to specify per directories access rights. By default (and as an example), the user can easily say that a directory is public, for frenchies only or for frenchies excepted those in the ripoux.fr domain (french joke!).

The user is also able to share his directories with other RearSite users (trusted users). When a directory is shared, a trusted user user is able to delete, rename, add ... files within the directory he received rights for.

The user is also able to recursively process all the file names of all his embeded directories. The functionality provided is to rename all files (lowercase, replace a string within all file names, ...) which simplyfies migration from systems with case-insensitive file names. These functionalities are available by selecting the Special tools button which also give a way to export the current directory within an archive (ZIP or tar.gz).

Since 1.4, a forum can directly be attached to each directories. When a user wants to create a forum, the result is a Forum.html file located within the current directory. This file will give access to the forum. People having access to this file are allowed to post in the forum.

Since 1.6, a chat can directly be attached to each directories. When a user wants to create a chat, the result is a Chat.html file located within the current directory. This file will give access to the chat. People having access to this file are allowed to talk in the chat.

Since 1.9, a shareable calendar can be directly attached to each directories. When a user wants to create a calendar, the result is a Calendar.html file located within the current directory. This file will give access to the calendar. People having access to this file are allowed to read the calendar. Only the owner of a calendar is allowed to update it, but he may allow other users. Accessing his calendar via RearSite allows the owner to update it immediatly. When accessing a calendar via a normal WWW access, the user (owner or not) must be authenticated (via Rearsite configured authentication scheeme) before being allowed to update it.

The chat,forum and calendar functionalities are accessible via the Communications button, they have been designed for distance learning purposes but can easily be used for any groupware needs.