Free vesta 1.0b software for linux

wrapmin is a wrapper that makes it possible to access Webmin from a directory on a site on an another Web server.

wrapmin is very useful if you are behind a firewall that only allows access to port 80.

EasyHTTPD is a drop in C++ class to implement an HTTP 1.0 Server - Now with OpenSSL Support! The class can be used to allow an application to be controlled by a browser, hence Embedded.
To this functionality to an app, add the C++ class to the application, write and register request callback handlers with the class, and call the parser with a connected socket.
The parser will extract any options passed in the URL, extract POST values, and call the desired handler.
The handler get a pointer to the application via void ptr, has haccess to the extracted options and POST values, and then write the desired output back to the socket.
For easy dynamic page generate, an HTML template file can be used, and the handler simply specifies token tags in the template to be replace with the dynamic values (aka search and replace )
HOW TO USE IN YOUR APPLICATION:
These classes use the STL (Standard Template Library), so your enviroment must have the STL available.
Add the embedhttp.cpp file to your project, and the embedhttp.h file to the file(s) in your project that handles incomming socket connections.
See the sample1.cpp and helloworld.cpp files to get an idea of how to use these classes.
Enhancements:
- Removed regex as a dependency. Regex library is no longer needed.
- Added member functions to do the following:
o Get the client headers
o Send headers back to the client
o Specify alternate socket send/recv functions to support use with OpenSSL
o Specify a pre-request handler, a handler that can be called for all requests before the specifc request handler get called
- Fixed bug in helloworld_template.html.
- Fixed bug in parse which occured when the client did not send any headers.
- Added hello world sample using OpenSSL.
- Added the wiki: http://www.littletux.com/wiki

DDNSNotify is a program that logs into a (telnet-enabled) router and retrieves the WAN IP address, but only if the IP address differs from the DNS (A record) address for the domain name given.

It is intend for DynamicDNS applications, where the IP address for a Web site changes (usually due to ISP rules). Thus, using the new IP address, you can update your DNS records using another external script (such as zoneclient.py), so that your Web sites downtime is reduced to a minimum.

The project currently supports Draytek Vigor routers (and possibly other Draytek models).

Jiplet is short for Java SIP Servlet. Jiplet Container project is an open-source container for server-side SIP applications. An application developer can create a SIP application written in Java using the Jiplet API and deploy the application in the container.
The container provides a number of framework services including support for SIP message parsing and formatting, scoped variables, authentication and authroization, thread-pooling, logging, custom class loading, management interface, etc. It enables application developer to create server-side SIP applications using a component-based model similar to that envisioned by the J2EE architecture.
In fact, it fits very well with the J2EE paradigm for software development and deployment. The jiplet container software can either be run as a standalone Java application or deployed as a service residing in a J2EE server. When running as a J2EE service, the jiplet container can access many of the features offered by the J2EE server.
In addition, The jiplet container is built with the service provider model in mind. In this model, a service provider can host customized SIP applications from their customers in a secure manner similar to the servlet hosting offered by many service providers.
The jiplet container is very similar to a Java HTTP servlet container in concept. A Java HTTP servlet is a Java class that handles HTTP messages from web browsers. Similarly, a jiplet is a Java class that handles SIP messages from SIP user agents (SIP phones and SIP servers).
A servlet container like Apache Tomcat can host one or more web applications (contexts), each consisting of one or more servlets. Similarly, the jiplet container can host one or more SIP applications (contexts) consisting of one or more jiplets.
Similar to the servlet API authored by Sun Microsystems, the jiplet container provides a set of Java classes that jiplet applications extend or use. The services provided by these classes are very similar to those of the servlet API including scoped variables, request forwarding from one jiplet to another, etc.
As in a servlet container, new jiplet applications, or contexts, can be deployed using a zipped file called spr (war is the Java servlet terminology). Since there are differences between the HTTP and SIP protocols, the servlet and the jiplet containers have some notable differences.
However, the jiplet is not a formal specification like the servlet specification. It is also not an implementation of the SIP servlet specification (JSR 116) authored by Sun and its community of users. There are many similarities between the jiplet and the SIP servlet in terms of features. If you are familiar with SIP servlets, you will feel right at home with the jiplet container.
We are planning to continue developing the jiplet container based on feedback provided by that the open-source community. We are hoping that open-source developers will extend this tool and the specification instead of a committee.
Main features:
- Open-source API for developing server-side SIP applications. Based on the JAIN-SIP API.
- Offers component-based development model.
- Servlet-like development and runtime environment.
- Access to powerful JAIN-API from SIP applications.
- JMX management interface for interfacing with management systems.
- Web-based user interface for managing jiplet applications.
- Support for scoped variables including application, session, request, transaction and dialog-scoped variables.
- Support for forwarding SIP messages from one jiplet to another.
- Container-managed authentication and authorization.
- Support for application timers.
- Can run as a standalone application or it can be integrated with JBOSS as a J2EE service.
- Comprehensive support for the service-provider model.
Enhancements:
- The final release (version 1.2) of the NIST SIP stack Reference Implementation has been incorporated into the Jiplet Container and reference applications.
- The new listening point architecture has been integrated into the Jiplet Container SIP connector.
- One connector can now use more than one IP address for SIP messaging.
- Convenience methods have been added to the Jiplet class for jiplet developers to handle additional listening points and SIP providers.
- The Jiplet Container message proxying has been updated to work in a multi-homed environment.
- The software has been tested with Jboss 4.0.5.GA.

The Monitor application, which consists of 2 parts, a MonitorServer (linux daemon) and a MonitorClient (java gui), will enable the user to monitor and log server process, memory, network and cpu information of multiple servers at a time.

The MonitorClient part is written in Java and is able to connect to one or more Servers that are running the MonitorServer part of the Monitor application.

The client will poll the servers at user specified intervals and will provide a graphical representation of the recources (mem, cpu, nic and process information) of one server at a time.

In addition the MonitorClient is able to log the information of all the servers, each server in a different logfile in a coprehesive CSV format.

The MonitorServer is a seperate application written in C++ and linked to omniORB4 to minimize the load it imposes on the server that is beeing monitored. When the MonitorServer is not beeing polled by a MonitorClient it sits idle.

The client will of course run on any platform that supports Java, but the server currently only supports Linux, kernels 2.2, 2.4, 2.6 and possibly (not tested) 2.0 and >2.6.

Yet Another Random Perl Portal (YARPP) is a simple Web portal environment. Yet Another Random Perl Portal is specifically designed to provide a portal that can be used to remotely manage small scale firewall products, such as net Juniper (Netscreen) 5 series devices.
As such, it includes configuration modification utilities, as well as traffic reporting components. It was designed to allow people to manage and monitor these firewalls while ensuring that all of the filter modification functions that are available via the devices native interface are removed from the user.
Enhancements:
- The module send_ssh_command.pl allowed execution of arbitrary commands on the Web server through manipulation of its input variables.

Vamos software allows computers to run software directly from the network, without installations. The software is stored on servers and is centrally maintained without the users effort or attention.

rootz is a new no install system that works differently. It mounts complete live systems over the web, and make them available locally. With rootz you can attach your local linux system to various livecds and simply run applications without any installation.

rootz is connected to the desired image (iso or squashfs), and uses rootz:// links to launch applications. The main advantage of this system, is that it uses unchanged official software without any repackaging (as opposed to klik, zero install or autopackage). Moreover, it is a true "on demand" mechanism that does not require full download of the software but fetches only the needed files. rootz can set up multiple isolated chroot environments, so it is possible run stable application side by side with new bleeding edge software.

Installation:

as non-root:
wget http://vamosproject.com/upload/rootz/install -O -| sh

Setup

The syntax is: rootz url.of.iso/.squash mountpoint

Examples:

Vamos client:
sudo mkdir /mnt/vamos
sudo ~/rootz/rootz http://vamosproject.com/upload/vamos-client-1.0b.squashfs /mnt/vamos

From this chroot you can run frozen bubble
Ubunutu Feisty Fawn:
sudo mkdir /mnt/feisty
sudo ~/rootz/rootz http://cdimage.ubuntu.com/cdimage/releases/feisty/herd-2/feisty-desktop-i386.iso /mnt/feisty

From this chroot you can run gaim
Debian Live with XFCE:
sudo mkdir /mnt/debian-live
sudo ~/rootz/rootz http://live.debian.net/daily-builds/current/i386/debian-live-sid-i386-xfce-desktop.iso /mnt/debian-live

From this chroot you can run thunar
Ubuntu "Ultimate":
sudo mkdir /mnt/ultimate
sudo ~/rootz/rootz http://fly5.pp.fi/ultimate/ubuntu-ultimate1.1.iso /mnt/ultimate

From this chroot you can run Democracy player

Run

You just need to click on those rootz:// links above, and wait... After few runs the page cache will contain common libs and files so applications will run faster.

Another option is to rootz-launcher in the command line interface. With this script you will be able to run non-gui programs.

Example:

~/rootz/rootz-launcher dpkg -l