Free iis software for linux

Lire is an Open Source reporting and analysis software, and serving as a nexus of documentation, ideas, and thought on the topic of log files and their potential applications.
As any good system administrator knows, theres a lot more to keep track of in an active network than just webservers. Lire is hands down the most versatile log analysis software available today. Lire not only keeps you informed about your HTTP, FTP, and mail traffic, it also reports on your firewalls, your print servers, and your DNS activity. The ever growing list of Lire-supported services clearly outstrips any other software, in large part thanks to the numerous volunteers who have pioneered many new services and features. Lire is a total solution for your log analysis needs.
Lire automatically generates useful reports from raw logfiles from various services.
Currently:
- exim
- sendmail
- qmail
- postfix
- bind
- apache
- boa
- IIS
- cisco ios
- ipchains
- ipfilter
- wu-ftpd
- proftpd
- cups
- lprng
log files are supported. Reports can be generated in simple ascii format, as well as in (x)html or pdf. Logs can be read from the local system in a cronjob, or can be received via email.

Fruit Show is a minimalist forum package based on the forums at joelonsoftware.com. Fruit Show is based on the philosophy that social atmosphere is a by-product of software design.
Theres no registration and very few features for visitors. Its skinnable and easy to install. It also contains some unique moderation features.
Fruit Show is intended for small sites that need an easy to use and accessible forum.
Enhancements:
- This release of FruitShow fixes a large number of issues and makes a few improvements to IIS support and support for PHP5.
- Smarter topic locking and improved optimization were added.

GeboGebo is a wiki system written for tdbengine. It stores all data in a local database structure and thus provides an indexed fulltext search.
GeboGebo is available for free download. It runs on Linux and with a little handwork on Windows 32-Bit as well. The name GeboGebo derives from the Germanic rune gebo, which means as much as "Giving and taking". This is the philosphy of a WikiWiki and is so perfectly with this name.
Due to massive spamming we decided to lock pages for anonymous edit. If you would like to test GeboGebo please register and then login or use the user account "Guest" whose password is "Guest". The sandbox is waiting for you to play around.
For installation of GeboGebo:
Ensure you have a working tdbengine installation. If you dont, better read those Link instructions or this Link German tutorial for IIS setup (with loads of screenshots).
unpack the gzipped tar-archive into your www-root directory
enter the gebo directory on console and run ./make.sh
open your web browser and enter the URL leading to your GeboGebo installation directory
Main features:
- The Automatic Link System links pages by their names without explicitely having to be marked as link
- GeboGebo stores all data in a database structure providing high performance data access by using intelligent indexes.
- brings its own mini http server which makes installation very easy
- The indexed fulltext search makes information retrieval a breeze.
- Pages can be renamed at any point of time, without any loss of information.
- All activities get locked and earlier revisions of pages can be restored from each pages infinite history.
- GeboGebo is capable of providing all information as static pages for faster read access and better indexing possibilities for 3rd party diggers.
- The user management is simple but effective: allow or disallow anonymous access in whole or for several pages and enable or disable self registration of new users.
- The User list provides information on registered users and points to their personal wiki pages.
- A list of missing and a list of unreferenced pages help filling content gaps in your wiki
- Fill a blacklist with patterns of wiki page names that may not be edited, if already existing, or even may not be created, if they do not already exist.
- File and Image uploading makes GeboGebo the perfect system for your simple document management.
- Users can subscribe to pages and get informed via EMail when those pages are changed.
- RSS feeds for your news aggregator
- Namespaces support you in dividing your Wiki into independend sections.
- Macros and plugins open all possibilities of tdbengine programming to you and your Wiki
- Link meatball>InterWiki links help you to reference information in other widely known wikis
- GeboGebo is released under the terms of the GNU General Public License (GPL).
Enhancements:
- due to a missing sub directory the minihttp server could not start before gebogebo had been running at least once on another web server before. Fixed.
- new switch CreateStaticIndex in the configuration now allows decisions made concerning the automatic index.html file creation (thanks for the tip to Malcolm)
- bug fix for the subscription list which before returned a blank page caused by an internal error (thanks to Malcolm)

SKForum project is a forum application with a Wiki, comic system, guestbook, and address book.
SKForum is an open source (see licensing) web-based J2EE forum application. But its so much more, its a comic system, an addressbook, a wiki, a timetracking system, a todo list, a poll system, a guestbook system and a few other small nuts and bolts.
SKForum was first taken into use in september of 2000. By july of 2001 it had grown to 6 464 lines of code, and at october 2003 it is at 49 067 lines total. Of these 37 596 are java source file lines.
Internationalization
SKForum has i18n support and supports the following languages:
- English (US)
- Swedish (SE)
- French (FR)
Installation howto
1. Install mysql.
2. Create a database in mysql called "forum".
3. Install Java 2 SDK
4. Install a J2EE servlet container, I recommend Resin 2.x (it is also a webserver and can be integrated with IIS or Apache if you want)
5. Get the SKForum WAR file.
6. Make sure theres no caching done on the forum, resin for example has a default caching setting, remove the part of the config.
7. Install the forum as a toplevel app. It will currently not work unless "/" leads to its own top level.
8. Set up the data sources. If needed install the JDBC driver in the servlet container (get the mysql driver here).
Setup data source in Resin 2.x
Setup data source in Resin 3.x
Setup data source in Orion
9. This step only if you do not use Resin: If you use tomcat, remove web.xml and rename tomcat-web.xml to web.xml. Otherwise comment out the parts of web.xml that is marked "resin specific" that your server does not support.
10. Get the mysql jdbc driver and put it in your app servers lib directory.
11. Login with the username and password you want for the admin account. The first person who logs into the forum will get full rights and be set up as admin by default.
Enhancements:
- features:
- tasks system added
- description field for areas
- add/remove areas to/from hotlist inside the area
- invitation support for user groups
- planning warns for close events in the hotlist
- custom area type: quotes
- custom area type: pictures
- custom area type: links
- wiki URL rewriting for good wiki URLs
- editing and posting redirects instead of forwards, no more issues with reposting
- added login success/failure logging to database
- bugs:
- checkbox bug in IE fixed
- user addition delay fixed
- fixed address book VCS export for OS X
- planning info box at the bottom displayed at the top
- subscribe broken for comics
- shows deleted status for single-line messages in dynamic collapsing mode
- access rights to areas were ignored
- issue with hotlist resolved
- cant write in empty area
- editing of planning events sometimes fail
- sorting in archive is by unicode, not by character
- improvements:
- switched all maps and arrays to use fastutil
- zip download for archive give a good filename

• Small - The complete content management system is less than 100 KB.
• Simple - simple to install and easy to modify. The entire site is stored in a single HTML-file - no database is needed. You edit your entire site with your favorite HTML-editor, upload the content file and get a dynamic website!
• Smart - There is an integrated online WYSIWYG (What-You-See-Is-What-You-Get) editor with link validation, image handling, online editing of system files and an automatic backup on logout. These features that makes CMSimple simply smart!

Major Features:

1. Easy installation
2. The CMS script is less than 100 KB
3. Template driven layout using a css script
4. The contents of the site is stored in a single HTML-file
5. Many languages available (both for the user and for site maintenance)
6. Written in PHP - it runs on Linux/Apache servers, or on Win32 with Apache or IIS
7. Inbuilt WYSIWYG editor (both on IE and Mozilla) - or other alternative editors
8. Uploading of images and files
9. Link validation
10. Search function
11. Print version option
12. User downloads from their HTML content file
13. Simple mailform included
14. Easy setup of multi language sites
15. PHP-scripting may be included within the content (named CMSimple Scripting)
16. Integration with 3rd party scripts possible (using CMSimple scripting)
17. Online editing of system configuration
18. wwwaut login available
19. Automatic backup on logout

Requirements:

• Requirements:
• • CMSimple is recommended for sites with text contents less than 2 MB - This is about 1000 pages of text (about 2,000 characters per page). There is no maximum size to the site but speed will become an issue. Photographs are stored separately, there is no limit to the number of photographs you can use. You are only restricted by the capacity you have bought from your ISP, and by limitations imposed by your PHP settings.
  • Editing of the files is normaly done on your local machine, using a normal browser (see below). You will also need an FTP program (like WS_FTP or WinSCP) to upload the files to your webserver.
• Server requirements
• • CMSimple is written in PHP. Thus, PHP >= 4.0.4 is required on your server. To install PHP on a webserver, you must have administrator rights. Many webhotels offer PHP as part of their standard service.
  • CMSimple runs on a Linux server under Apache, or on Win32 under Apache or IIS. It also runs on Abyss. No database is needed as the entire site contents are stored in a single HTML-file.
• WWW-Authenticate
• • For better password protection it is advised to use wwwaut.
  • On Linux where PHP is installed as an Apache module (not a CGI), this feature will work just by setting wwwaut to 'true' under the configuration settings of CMSimple.
• The WYSIWYG online editor
• • The editor works with new versions of IE, Firefox and Opera.
  • The WYSIWYG online editor does NOT work with Safari, old versions of Opera, Firefox < 1.0 or IE5.
  • The inbuilt WYSIWYG online editor is written in JavaScript. It was formerly known as OEdit.
  • Though the final result of an edit can be viewed by all browsers, the editing can only be done with the following browsers. Linux: Mozilla 1.3 and above.

Enhancements:

• Several language codes have been changed for language/flag files to comply to ISO 639-1 language codes.
• All languages are available from the new download form, and all languages have a flag.
• The licence text in files was changed.
• The Hungarian translation was updated.
• A "readme.txt" file was added in the downloads directory.

Greenstone is a suite of software for building and distributing digital library collections. It provides a new way of organizing information and publishing it on the Internet or on CD-ROM.
Greenstone is produced by the New Zealand Digital Library Project at the University of Waikato, and developed and distributed in cooperation with UNESCO and the Human Info NGO.
Greenstone is open-source, multilingual software, issued under the terms of the GNU General Public License.
The aim of the Greenstone software is to empower users, particularly in universities, libraries, and other public service institutions, to build their own digital libraries. Digital libraries are radically reforming how information is disseminated and acquired in UNESCOs partner communities and institutions in the fields of education, science and culture around the world, and particularly in developing countries. We hope that this software will encourage the effective deployment of digital libraries to share information and place it in the public domain.
Enhancements:
- This release fixed authentication bugs on Windows and bugs in the remote GLI.
- Interface improvements were made in GLI.
- New NoText metadata can be used to suppress the dummy text.
- The remote GLI now works on IIS 6.
- Open on the File menu is now disabled while a collection is loading to prevent exceptions.
- You can now double click an index to bring up the Edit Index window.
- Catalan and Vietnamese GLI interfaces were added.
- There were also other improvements and bugfixes.

NS WebMail project is a simple set of PERL scripts, it works using module Mail::POP3Client, and allows to send and receive MIME compliant mails.
The whole thing is "secured" using POP3 authentication, ie mail cant be send or retrieved without initial correct authentication.APOP and standard PASS authentication work.
No need of any SQL base and so on. However, better know how PERL and CGIs work ! This allows NSWM to remain simple and light, and not to require an important set of PERL modules.
NSWM now support two kinda security improvments:
- HTTP Auth: just configure your Apache to authenticate user with normal HTTP Auth. Then you
need to use indexauth.pl instead of index.html as a start page, and run NSWM in mod_perl.
It works automatically.
- Cookie stored key: the key used to encrypt the password may be stocked partially in a cookie.
This prevents bad guys from accessing other users inboxes when they used shared computers.
You have to enable this feature in the configwm.pm file, at "cookiedomain": enter your
domain to enable the feature, comment the line out to disable.
Both security features will work over HTTPS.
Supported languages
Modules exists and languages have been tested for:
- English (lang-en.pl module, core module)
- Francais (lang-fr.pl module, dev module)
- Russian (lang-ru.pl module, dev module)
- Hrvatski (lang-hr.pl module, trn module from dpavlin at rot13.org)
- Deutsch (lang-de.pl module, trn module from Tobias.Mueller at stud.uni-hannover.de)
- Norwegian (lang-no.pl module, trn module from erlingp at f00bar.fagmed.uit.no)
- Hungarian (lang-hu* modules, trn module from keve_g at mail.takarek.net)
- Swedish (lang-se.pl, trn module from hm at nool.nu)
- Czech (lang-cz.pl, trn module from svasek at nextra.cz)
- Italian (lang-it.pl, trn module from theos at bp.lnf.it)
- Spanish (lang-spl.pl, trn module from scristi at startlight.com)
- Portuguese (lang-pt.pl, trn module from luiz at pucrs.br)
- Romanian (lang-ro.pl, trn module from chally_ro at yahoo.com)
Anyone translating the langpack in another language is asked to send it us, please !
This way we can improve NSWM.
installation
1- Unzip it:
On performant UNIX (with recent gnu tar), do a tar xvzf nswm-XXXXXX.tar.gz
On Windows, use Winzip or PowerArchiver (http://www.powerarchiver.com)
2- Set up your favorite HTTP server to handle the application.
For Apache:
=> put an Alias section as /nswm for the nswm/html directory
=> put a ScriptAlias section as /nswm/cgi-bin for the nswm/cgi-bin directory
For IIS,NES:
Use the graphic interface to set it up properly. Refer to server documentation.
3- Then you have to edit configwm.pm file and specify your SMTP server ($SMTPserver variable).
Words and paths can be set up in config.pl file.
You can also choose the language.
Nota: configwm.pm template is configwm.pm.dist.
4- PERL Modules to install if not installed:
Dont forget to install them (example with Mail::POP3Client):
=> perl -MCPAN -e install Mail::POP3Client on UNIX (or see at http://www.cpan.org)
or ppm Mail-POP3Client on WNTs ActivePerl (but better see at http://www.activetsate.com)
The following modules/packages are needed:
IO-stringy,MIME-Base64,MIME-Lite,MIME-tools,MailTools,Mail::POP3Client,TimeDate,URI,CGI
(yeah, thats a lot, i know. MIME encoding/decoding isnt a simple thing...)
5- Misc install things:
Dont forget to chmod 777 (or, better, chown apache or nobody or www-data) the /var/opt/nswm/log and
/var/opt/nswm/tmp directories if you dont change those locations in the configwm.pm file.
You can do a small cron script to launch bin/nswmcron to enable the automatic cleanup of temp files (This is automatically done by the RPM). Dont forget to change the html/title.htm file....
Enhancements:
- Several improvements in mail header decoding in the inbox.
- Optional ability to report spam to spam software (tested and documented with SpamAssassin).
- Full management of the "Urgent header".

CGI::Portable is a framework for server-generic web apps.

SYNOPSIS

Content of thin shell "startup_cgi.pl" for CGI or Apache::Registry env:

#!/usr/bin/perl
use strict;
use warnings;

require CGI::Portable;
my $globals = CGI::Portable->new();

use Cwd;
$globals->file_path_root( cwd() ); # let us default to current working directory
$globals->file_path_delimiter( $^O=~/Mac/i ? ":" : $^O=~/Win/i ? "" : "/" );

$globals->set_prefs( config.pl );
$globals->current_user_path_level( 1 );

require CGI::Portable::AdapterCGI;
my $io = CGI::Portable::AdapterCGI->new();

$io->fetch_user_input( $globals );
$globals->call_component( DemoAardvark );
$io->send_user_output( $globals );

1;

Content of thin shell "startup_socket.pl" for IO::Socket::INET:

#!/usr/bin/perl
use strict;
use warnings;

print "[Server $0 starting up]n";

require CGI::Portable;
my $globals = CGI::Portable->new();

use Cwd;
$globals->file_path_root( cwd() ); # let us default to current working directory
$globals->file_path_delimiter( $^O=~/Mac/i ? ":" : $^O=~/Win/i ? "" : "/" );

$globals->set_prefs( config.pl );
$globals->current_user_path_level( 1 );

require CGI::Portable::AdapterSocket;
my $io = CGI::Portable::AdapterSocket->new();

use IO::Socket;
my $server = IO::Socket::INET->new(
Listen => SOMAXCONN,
LocalAddr => 127.0.0.1,
LocalPort => 1984,
Proto => tcp
);
die "[Error: cant setup server $0]" unless $server;

print "[Server $0 accepting clients]n";

while( my $client = $server->accept() ) {
printf "%s: [Connect from %s]n", scalar localtime, $client->peerhost;

my $content = $globals->make_new_context();

$io->fetch_user_input( $content, $client );
$content->call_component( DemoAardvark );
$io->send_user_output( $content, $client );

close $client;

printf "%s http://%s:%s%s %sn", $content->request_method,
$content->server_domain, $content->server_port,
$content->user_path_string, $content->http_status_code;
}

1;

^The CGI::Portable class is a framework intended to support complex web applications that are easily portable across servers because common environment-specific details are abstracted away, including the file system type, the web server type, and your projects location in the file system or uri hierarchy.

Also abstracted away are details related to how users of your applications arrange instance config/preferences data across single or multiple files, so they get more flexability in how to use your application without you writing the code to support it. So your apps are easier to make data-controlled.

Application cores would use CGI::Portable as an interface to the server they are running under, where they receive user input through it and they return a response (HTML page or other data type) to the user through it. Since CGI::Portable should be able to express all of their user input or output needs, your application cores should run well under CGI or mod_perl or IIS or a Perl-based server or a command line without having code that supports each types individual needs.

That said, CGI::Portable doesnt contain any user input/output code of its own, but allows you to use whatever platform-specific code or modules you wish between it and the actual server. By using my module as an abstraction layer, your own program core doesnt need to know which platform-specific code it is talking to.

As a logical extension to the interfacing functionality, CGI::Portable makes it easier for you to divide your application into autonomous components, each of which acts like it is its own application core with user input and instance config data provided to it and a recepticle for its user output provided. This module would be an interface between the components.

This class has 5 main types of functionality, or sets of properties that exist in parallel but are fully/mostly independant from each other. As such, it could conceptually be split into 5 physical modules, some of which could be used on their own, but they are actually contained in this one module for simplicity of use (just one object for user code to keep track of). The 5 functionality sets could be called: Errors, Files, Request, Response, Misc.