Free admin area software for linux

iNet Admin Daemon interacts with services such as an Apache2 load balanced environment, a MySQL 5 clustered environment, PureFTPD, PowerDNS, Cacti, Nagios.
iNet Admin Daemon has various other services to create central ease of management and integration with these services for hosting companies.
Enhancements:
- Functional modules were added for existing services connecting to DBmail, PowerDNS, Apache2, and MySQL 5.

SQL Admin is a Java client application to connect and send queries to different databases through JDBC.
SQLAdmin uses the brand new SWT Toolkit. The main idea is to create a multiplatform and multidatabase thin client. For example, you can connect to an Microsoft SQL Server from a Linux machine, or connect to a PostgreSQL/Linux server from a Windows machine using the same application.
Main features:
- Based on the SWT Tookit. Java applications can use the native Toolkit with a platform independant API. For example, SQLAdmin uses GTK2 in Linux
- Lightweight : The application itself is small, and the SWT provides a nice gui with a very small footprint
- Abstract JDBC driver backend. User should configure only basic parameters like server, port, and login without the need to know about Class names or JDBC URLs
- Graphical view of connections and database metadata such as schemas, tables and fields
- Multiple query execution. Also supports embedded comments on SQL Text
- Log window to view system messages and query results
- Table structure view
- Fast table rows view

IMAP::Admin is a Perl module for basic IMAP server administration.

SYNOPSIS

use IMAP::Admin;

$imap = IMAP::Admin->new(Server => name.of.server.com,
Login => login_of_imap_administrator,
Password => password_of_imap_adminstrator,
Port => port# (143 is default),
Separator => ".", # default is a period
CRAM => 1, # off by default, can be 0,1,2
SSL => 1, # off by default
# and any of the SSL_ options from IO::Socket::SSL
);

$err = $imap->create("user.bob");
if ($err != 0) {
print "$imap->{Error}n";
}
if ($err != 0) {
print $imap->error;
}
$err = $imap->create("user.bob", "green");
$err = $imap->delete("user.bob");
$err = $imap->h_delete("user.bob");

$err = $imap->subscribe("user.bob");
$err = $imap->unsubscribe("user.bob");

$err = $imap->rename("bboard", "newbboard");

@quota = $imap->get_quotaroot("user.bob");
@quota = $imap->get_quota("user.bob");
$err = $imap->set_quota("user.bob", 10000);

@acl = $imap->get_acl("user.bob");
%acl = $imap->get_acl("user.bob");
$err = $imap->set_acl("user.bob", "admin", "lrswipdca", "joe", "lrs");
$err = $imap->delete_acl("user.bob", "joe", "admin");

@list = $imap->list("user.bob");
@list = $imap->list("user.b*");

$imap->{Capability} # this contains the Capabilities reply from the IMAP server

$imap->close; # close open imap connection

IMAP::Admin provides basic IMAP server adminstration. It provides functions for creating and deleting mailboxes and setting various information such as quotas and access rights.

Its interface should, in theory, work with any RFC compliant IMAP server, but I currently have only tested it against Carnegie Mellon Universitys Cyrus IMAP and Mirapoints IMAP servers. It does a CAPABILITY check for specific extensions to see if they are supported.

Operationally it opens a socket connection to the IMAP server and logs in with the supplied login and password. You then can call any of the functions to perform their associated operation.

Separator on the new call is the hiearchical separator used by the imap server. It is defaulted to a period ("/" might be another popular one).

CRAM on the new call will attempt to use CRAM-MD5 as the login type of choice. A value of 0 means off, 1 means on, 2 means on with fallback to login. *Note* this options requires these perl modules: Digest::MD5, Digest::HMAC, MIME::Base64

SSL on the new call will attempt to make an SSL connection to the imap server. It does not fallback to a regular connection if it fails. It is off by default. IO::Socket::SSL requires a ca certificate, a client certificate, and a client private key. By default these are in current_directory/certs, respectively named ca-cert.pem, client-cert.pem, and client-key.pem. The location of this can be overridden by setting SSL_ca_file, SSL_cert_file, and SSL_key_file (youll probably want to also set SSL_ca_path).

I generated my ca cert and ca key with openssl: openssl req -x509 -newkey rsa:1024 -keyout ca-key.pem -out ca-cert.pem
I generated my client key and cert with openssl: openssl req -new -newkey rsa:1024 -keyout client-key.pem -out req.pem -nodes openssl x509 -CA ca-cert.pem -CAkey ca-key.pem -req -in req.pem -out client-cert.pem -addtrust clientAuth -days 600

Setting up SSL Cyrus IMAP v 2.x (completely unofficial, but it worked for me) add these to your /etc/imapd.conf (remember to change /usr/local/cyrus/tls to wherever yours is) tls_ca_path: /usr/local/cyrus/tls tls_ca_file: /usr/local/cyrus/tls/ca-cert.pem tls_key_file: /usr/local/cyrus/tls/serv-key.pem tls_cert_file: /usr/local/cyrus/tls/serv-cert.pem
For my server key I used a self signed certificate: openssl req -x509 -newkey rsa:1024 -keyout serv-key.pem -out serv-cert.pem -nodes -extensions usr_cert (in openssl.cnf I have nsCertType set to server)
I also added this to my /etc/cyrus.conf, it shouldnt strictly be necessary as clients that are RFC2595 compliant can issue a STARTTLS to initiate the secure layer, but currently IMAP::Admin doesnt issue this command (in SERVICES section): imap2 cmd="imapd -s" listen="simap" prefork=0
where simap in /etc/services is: simap 993/tcp # IMAP over SSL

PAiN project is a new MUD code base written in Java.
PAiN is a new MUD codebase written in Java. It provides a general purpose persistence engine (PAiN DB) and the ability to do dynamic code reloading.
Main features:
- Pure Java database engine (transparent constant-time object access, tracking of the dirty state, transactions and savepoints support).
- Static server code (connection handling, support for code reloading and base interfaces).
- Dynamic reloadable set of action classes and plugins (virtual world logic code and plugins).
- Graphical tool to administrate server and database
Enhancements:
- PAiNDB: Collections could be saved separately from object image.This option should be used if collection is not the only field of dbobject, it has size of 20-40 items and dbobject fields are changed often. Saving collection separately will reduce flushing and object backup time inside transactions.
- PAiNDB: DbObject.provideSchema() is now static method and required for all non-abstract DBObject impls. This allows to import class schema into db without object instantiation.
- GUITool: fully rewritten, modules concept added.
- Codebase: more admin console commands.
- Tinylyb: roles removed: Reset, ResetGroup. SpaceGroup was renamed to Area.
- Tinylib: more shell implemented(this shell should be used to show multipage output)
- Tinylib: online builder bugfixing.
- PAiNDB: fixed bug with error on objects removal with non-empty StringMap type fields.
- Tinylib: bugs in @build mode fixed. More complete visualization for array-type fields
- Tinylib: number of small enhancements.

OpenVISP Admin project is a fork of Postfix Admin.
As administrator of a highly centralized and industrial grade hosting system, I need some webinterface to update data on a SQL database.
First I have used Postfix Admin to manage mail data but I was looking for more specialized system that is not a system that takes hours and is not configurable...
So I have started to modify Postfix Admin to suits my needs and so on.
Why OpenVISP Admin ?
I dont like 3 things on current Postfix Admin :
- The new license that has moved from MPL 1.1 to another proprietary one
- The bloody webforums and the fact that no authors was interested by my patches
- No CVS / CVSweb to see changes between versions
So this is basicaly why I have started a fork of Postfix Admin.
Main features:
- Quota enforcement
- Domain aliases
- Antivirus Checkbox when creating domain
- Antispam Checkbox when creating domain
- Sender / Domain verification checkboxes when creating domain
- GreyListing Checkbox when creating domain
- Spam Assassing Tag
- Spam Assassin Tag score value
- Tranport value when domain is backup MX
- Be more user friendly eg one login password with rights to get what he is allowed to
- Allow Postmasters to get access to APC Masterswitch
- To be done :
- Adding mod_vhs option for FTP and Web servicing purposes
- Allow postmaster to modify per aliases and per mailboxes SA values, etc..
- Allow user to modify their SA values on their mailboxes but also on their aliases
- Allow users to see their weblogs
- Allow users to search in logs for rejected messages and the reason why
- Redesign auth system to be more flexible.
How will this works ?
Interface
All the web interface will store data into MySQL (or PostgreSQL but this is not tested, I need some testers for that). The data is replicated and interfaced to a LDAP with a back_perl.
OpenLDAP back_perl
The back_perl scripts will be released when OpenVISP Admin 1.0 will be released.
Enhancements:
- The setup of all directories has been changed to be more clear about docs and contrib.
- lmtpd filtering options have been added.
- There is a new module to handle Web and FTP hosting.
- Some parts of the Web interface have been changed.
- More security checks have been added.
- There are many other new features.

ARAs goal is to create simple but convenient solution for managing the FreeRADIUS server.
ARA is PHP web-app operating on FreeRADIUS storage (currently only MySQL database). Look on its overview and decide is it right tool for you.
Enhancements:
- Visual polishing and end-user experience improvements.
- An easy system to integrate RADIUS users private information.

JVending project bridges P2P networks and wireless delivery of content to mobile devices. Due to high latency of wireless connections, it is not practical to directly hook up the mobile devices to the peer network, so I have taken a different approach with JVending.

A user sets up a personal provisioning server on their PC and hooks it into the network. Through the P2P network, we create a federation of provisioning servers. The mobile devices use the federated provisioning servers as content portals.

JVending differs from P2P systems, such as Gnutella or "Project JXTA" reference implementation, in the following ways. JVending provides:

1. Catalog management
2. Device detection, which delivers the appropriate content based upon the type of browser or device
3. Web based browsing of content, so you can share with your friends on a wired or wireless network, after you have already collected the content.
4. The ability to search for and distribute packaged archives on the peer network.
5. Web links tying together the network.
6. PPG integration for pushing content to mobile devices.

For 2005 - 2006, the major goals of JVending (roughly in order of importance) are:

1. Expanding P2P support, including more in the area of wireless messaging (SMS)
2. JSR-124 compliance
3. Performance testing and monitoring capability
4. Multimedia server and J2ME support. This covers full integration between the MMS Client and the provisioning server.

Setting up the Environment

Follow these steps:

1. Make sure that you have J2SE 1.4.2 JDK installed. If not, go to http://java.sun.com/j2se/1.4.2/download.html and download and install the JDK (not JRE). I have not tested with J2SE 1.5 JDK, so it may or may not work with that version.
2. Download the jvending-standalone.zip file from the JVending project site.
3. Unzip the file into a directory of your choice, say /jvending
4. Set the JAVA_HOME environmental variable, depending on your OS. In windows, you can do this through the Control Panel/System/Advanced/Environmental Variable: JAVA_HOME =
EXAMPLE: JAVA_HOME=c:Programsj2sdk1.4.2_06

Starting JVending

1. Go to the bin directory and click on the run.bat (for windows) or run.sh for Unix.
2. The first time you start JVending, you will see a JXTA Configurator screen show up. Type in your user name and password/verify password. Click OK.
3. Wait 10 seconds for JVending to finish its startup sequence and then go to http://localhost:80/jvending/login. If you get a 404 error, wait a few more seconds and try again. Login ID/Password: admin/admin. Click "Submit Query" button. You will now see the JVending home page.