Free setpoint 3.3 xp software for linux

remoteMoin are a couple of XML-RPC plugins for MoinMoin adding some useful features making a automated usage of MoinMoin easier.
Installation:
Scripts
Installation of these mini-projects is straight-forward: Just put them in a directory in your path and make them executable.
Some mini-projects have prerequisites which are listed in the manual page. Make sure to have the prerequisites installed.
Perl modules
Perl modules are of course installed with the usual sequence of
gunzip < dist >.tar.gz
tar xvf < dist >.tar
cd < dist >
perl Makefile.PL
make
make test
make install
Emacs
Refer to the file itself how to embed the code into your Emacs environment.
MoinMoin
Some mini projects are plugins for MoinMoin and you must put them to the right directory in the plugin structure of your Wiki. For instance see installation instructions for parsers.
Other mini projects are regular scripts.
Please note that the current hoster of this site does not like .py files. Therefore they are extended by a .txt. Please strip the .txt before installation.
Enhancements:
- Adaptations for MoinMoin 1.5.4 (was 1.3.4).

ntop is a network traffic probe that shows the network usage, similar to what the popular top Unix command does.
The project is based on libpcap and it has been written in a portable way in order to virtually run on every Unix platform and on Win32 as well.
ntop users can use a a web browser (e.g. netscape) to navigate through ntop (that acts as a web server) traffic information and get a dump of the network status.
In the latter case, ntop can be seen as a simple RMON-like agent with an embedded web interface. The use of:
a web interface
limited configuration and administration via the web interface
reduced CPU and memory usage (they vary according to network size and traffic)
make ntop easy to use and suitable for monitoring various kind of networks.
Main features:
- Sort network traffic according to many protocols
- Show network traffic sorted according to various criteria
- Display traffic statistics
- Store on disk persistent traffic statistics in RRD format
- Identify the indentity (e.g. email address) of computer users
- Passively (i.e. withou sending probe packets) identify the host OS
- Show IP traffic distribution among the various protocols
- Analyse IP traffic and sort it according to the source/destination
- Display IP Traffic Subnet matrix (whos talking to who?)
- Report IP protocol usage sorted by protocol type
- Act as a NetFlow/sFlow collector for flows generated by routers (e.g. Cisco and Juniper) or switches (e.g. Foundry Networks)
- Produce RMON-like network traffic statistics
Additional features of "ntop":
- Network Flows
- Local Traffic Analysis
- Multithread and MP (MultiProcessor) support on both Unix and Win32
- Perl/PHP/Python lightweight API for accessing ntop from remote
- Support of both NetFlow andsFlow as flow collector. ntop can collect simultaneously from multiple probes.
- Traffic statistics are saved into RRD databases for long-run traffic analysis.
- Internet Domain, AS (Autonomous Systems), VLAN (Virtual LAN) Statistics
- Network assets discovery and categorization according to their OS and users
- Protocol decoders for most of known P2P (Peer to Peer) protocols
- Advanced per user HTTP password protection with encrypted passwords
- RRD support for persistently storing per-host traffic information
- Passive remote host fingerprint (Courtesy of ettercap)
- HTTPS (Secure HTTP via OpenSSL)
- Virtual/multiple network interfaces support
- Graphical Charts (via gdchart)
- WAP support

Sashenka is aJ2EE Servlet container and framework for IRC bots and clients.

Much of it is incomplete and it only handles basic incoming and outgoing messages but it is enough to build trivial bots with.

Bots are written as Servlets following the
Sun J2EE servlet model which are loaded by the container.

The container dispatches messages to and through the modules so that they may respond (if they so wish).

You could even build a functional IRC client with the utility classes in sashenka but there are enough of those out there already so I dont recommend that you try.

What sashenka does offer is an object oriented framework for managing IRC traffic. My only use for it is the bot framework built on top of the IRC framework.

The distro comes with the j2ee.jar from the 1.2.1 j2ee sdk. I include this for convenience, if you have the j2eesdk I encourage you to use your own copy as mine may not jive with your runtime.

This package provides a complete http client library. It currently implements most of the relevant parts of the HTTP/1.0 and HTTP/1.1 protocols, including the request methods HEAD, GET, POST and PUT, and automatic handling of authorization, redirection requests, and cookies.

Furthermore the included Codecs class contains coders and decoders for the base64, quoted-printable, URL-encoding, chunked and the multipart/form-data encodings. The whole thing is free, and licenced under the GNU Lesser General Public License (LGPL) (note that this is not the same as the GPL).

Following are the kits and documentation for the HTTPClient Version 0.3-3. If you have any problems, bugs, suggestions, comments, etc. see the info on debugging and reporting problems. An older version of these pages are also available in Japanese, thanks to the kindly efforts of Yuji Kumasaka.

Using the HTTPClient should be quite simple. First add the import statement import HTTPClient.*; to your file(s). Next you create an instance of HTTPConnection (youll need one for every server you wish to talk to). Requests can then be sent using one of the methods Head(), Get(), Post(), etc in HTTPConnection.

These methods all return an instance of HTTPResponse which has methods for accessing the response headers (getHeader(), getHeaderAsInt(), etc), various response info (getStatusCode(), getReasonLine(), etc), the response data (getData(), getText(), and getInputStream()) and any trailers that might have been sent (getTrailer(), getTrailerAsInt(), etc). Following are some examples to get started.
To retrieve files from the URL "http://www.myaddr.net/my/file" you can use something like the following:
try
{
HTTPConnection con = new HTTPConnection("www.myaddr.net");
HTTPResponse rsp = con.Get("/my/file");
if (rsp.getStatusCode() >= 300)
{
System.err.println("Received Error: "+rsp.getReasonLine());
System.err.println(rsp.getText());
}
else
data = rsp.getData();

rsp = con.Get("/another_file");
if (rsp.getStatusCode() >= 300)
{
System.err.println("Received Error: "+rsp.getReasonLine());
System.err.println(rsp.getText());
}
else
other_data = rsp.getData();
}
catch (IOException ioe)
{
System.err.println(ioe.toString());
}
catch (ParseException pe)
{
System.err.println("Error parsing Content-Type: " + pe.toString());
}
catch (ModuleException me)
{
System.err.println("Error handling request: " + me.getMessage());
}

This will get the files "/my/file" and "/another_file" and put their contents into byte[]s accessible via getData(). Note that you need to only create a new HTTPConnection when sending a request to a new server (different protocol, host or port); although you may create a new HTTPConnection for every request to the same server this not recommended, as various information about the server is cached after the first request (to optimize subsequent requests) and persistent connections are used whenever possible (see also Advanced Info).

To POST form data from an applet back to your server you could use something like this (assuming you have two fields called name and e-mail, whose contents are stored in the variables name and email):
try
{
NVPair form_data[] = new NVPair[2];
form_data[0] = new NVPair("name", name);
form_data[1] = new NVPair("e-mail", email);

// note the convenience constructor for applets
HTTPConnection con = new HTTPConnection(this);
HTTPResponse rsp = con.Post("/cgi-bin/my_script", form_data);
if (rsp.getStatusCode() >= 300)
{
System.err.println("Received Error: "+rsp.getReasonLine());
System.err.println(rsp.getText());
}
else
stream = rsp.getInputStream();
}
catch (IOException ioe)
{
System.err.println(ioe.toString());
}
catch (ModuleException me)
{
System.err.println("Error handling request: " + me.getMessage());
}

Here the response data is read at leisure via an InputStream instead of all at once into a byte[].

As another example, if you want to upload a document to a URL (and the server supports http PUT) you could do something like the following:
try
{
URL url = new URL("http://www.mydomain.us/test/my_file");

HTTPConnection con = new HTTPConnection(url);
HTTPResponse rsp = con.Put(url.getFile(), "Hello World");
if (rsp.getStatusCode() >= 300)
{
System.err.println("Received Error: "+rsp.getReasonLine());
System.err.println(rsp.getText());
}
else
text = rsp.getText();
}
catch (IOException ioe)
{
System.err.println(ioe.toString());
}
catch (ModuleException me)
{
System.err.println("Error handling request: " + me.getMessage());
}

pam_sotp PAM module provides support for One Time Passwords (OTP) authentication. The "s" in "sotp" stands for "simple"; pam_sotp aims to be a simple, easy to configure, module.
pam_sotp is still under early stages of development. Although it seems to work pretty well be warned that this software could contain severe bugs that may put at risk the security of your system. Until a stable release is reached you are advised to not use pam_sotp on mission-critical systems or production servers.
Having said that, it seems that the software is reaching an stable stage. Ive received several reports about pam_sotp being used without problems in several configurations.
This project is way too small to have a serious roadmap, but anyways I guess that some of you would like to know what are my short/medium term plans for pam_sotp, so here they are:
Release pam_sotp 0.4.0, with some patches I received and other improvements I have in mind
Maintain the 0.4.x branch until it becomes stable
Release a couple of 1.0 release candidates and then finally pam_sotp 1.0
Maintain the 1.0 branch
Enhancements:
- Added disable and enable commands to otppasswd
- Bugfix: SGID shadow applications could not authenticate against pam_sotp (some SUID code somehow remained in pam_sotp)

Templeet provides a powerful template engine.
Templeet is a very powerful template engine which allows you to create photo galleries, news systems, personal sites, blogs, etc.
You can use it to generate HTML, CSS, SVG pictures, SMIL, and any kinds of text files. It offers multiple levels of caches.
Templeets strong points are ease of install, performance, and increased productivity through multiple levels of cache. When all caches are activated, performance is similar to serving static pages, ie. around 400 hits/second on a PII 400Mhz processor.
Templeet, is distributed under the free Gnu Public License (GPL) and open source. The latest source code is available through CVS, and discussions about development can be held in the public mailing lists. We do welcome user feedback and additions.
The documentation is currently pretty thin and is mostly only available in French, but it should be enough to get you started... provided you do read French, of course. Wed be grateful to any kind soul who could take the time to translate it into English (note: it gets better, so you can still take a look).
Only a few examples of templates are provided, but they should be good enough to give you a rough idea of what you can do with Templeet. If you need help, members of the mailing lists could provide support in a timely manner. You can also take a look at the available packages, and if this is your first Templeet installation, we invite you to read the documentation.
Templeet only needs a web server (Apache) and PHP. It supports databases but none is needed to run Templeet.
Main features:
- Template system
- Complete file manager (file upload, download remote file)
- Template editor
- Minimal shell
- Full authentication management (using either: file, MySQL, PostgreSQL or ODBC)
- User management interface
- Package system, install and update
- Updating Templeet with administrators interface
- Secured template updates (non modification check since last update)
- Thumbnail generation with GD, GD2 or convert (ImageMagick)
- Full caching system. Near static pages performances
- Functions for HTML validity
- Definition of functions within templates, recursive calls possible
- Remote RSS stream management display
- Spell checker module
- Secured private information management.
- Templeet configuration management through a GUI
- Multilingual management, in the manner of Apache
- Works with Unix and Windows
- Full independent installer, no need to have an Internet connection while installing
- Weblog available as a package, no database needed
- Fitted for small personnal sites as well as huge sites serving millions of hits per day

Pubcookie is an Open Source package for intra-institutional, single sign-on, end-user Web authentication. More generally, it is an approach to identifying users as they browse to an institutions many websites that require authentication.
Pubcookie helps an institution reuse existing authentication services (like Kerberos, LDAP, or NIS), and it limits the exposure of end-user passwords by ensuring theyre only sent to a trusted login service.
Enhancements:
- Highlights of this release include a fix for duplicate HTTP Header values in the ISAPI filter, a fixed AES mode with inactivity timeout in the Apache module, checks to improve handling of reauthentication requests, a new PubcookieCatenateAppIDs directive in the Apache module, and a clear_username_at_logout site policy in the login CGI.
- New default HTML login templates were included.