Free mypink moebuntu 3 software for linux

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)

Ovidentia is a professional collaborative/groupware portal generator featuring an administrable management tool with a workflow for the approval to publish articles, comments, files, or vacation requests.
It also features an agenda (shareable), an integrated directory, charts, an LDAP directory interface, add-ons support, a mail interface, and a WYSIWYG HTML editor to publish articles, news, posts, or write email. The project supports LDAP, Ovidentia, and Active Directory authentication.
Enhancements:
- Bugs correction
- Security corrective measures
- Vacation requests management evolutions

pkdump is a port scanning detection tool. The program detect any TCP ,UDP port scanning or open connection attempt from foreign host over the internet with IP protocol version 4
or IP protocol version 6 .
The program can detect:
TCP connect , TCP syn , TCP fin , TCP xmas, TCP ack, TCP null(no flags), UDP port (connect) and UDP null (0 bytes, UDP packets lengt ) , whether the IP packet are fragmented or not. (Please consult "Nmap"... man Nmap).
The program make a directory like this : "Pkdump-[date][time]" and in this directory make a file "PKDATA" that contains all IP packet sent and received during the transmission ,and during scanning attack make files that contains the data of the attack ;the data of the port scanning will displayed on the screen with a short beep;
Enhancements:
- Fixed bug in read-write operation.
- Show the number of IP fragment.

Mp3blaster is an mp3 player for computers running a UNIX-like operating system, e.g. Linux, Free/Net/OpenBSD, etc. mp3blasters interface is entirely text based, thereby eliminating the need for a graphical environment like X-Windows.
This does not limit the way you can control the player whilst playing though; just like any graphical mp3 player, there are cd-style buttons like play, stop, pause, next track, etc.
While hardly anyone had ever heard of mp3 back in early 1997, I began to build up my own mp3 collection. As a Linux (text console) adept, I was heavily frustrated by the lack of a decent mp3 player. There was a (at the time) very popular command-line based mp3 player though, called splay. I figured I could use its mpeg decoding library and write my own interface in ncurses to control it. The plan was there!
Thinking about how to implement this interface, I also wondered why all mp3players had such plain playlist functionality! I like the ability to chuck a bunch of CDs in a multi-CD cd player, and then play the CDs in random order. In such a way that the cd player selects one of the five CDs at random, and then plays the entire disc. This continues, until all discs have been played. No mp3 player could do this, so I decided to add it to mine.
Enhancements:
- A parallel build bug was fixed. make -j now works.
- Dynamic screen resizing was implemented.
- A race condition that caused 100% CPU consumption at the end of each song was fixed.

Munin is a tool for graphing all sorts of information about one or more servers and displaying it in a web interface. Munin uses the execellent RRDTool (written by Tobi Oetiker) and is written in Perl. Munin has a master/node architecture.
The master connects to all the nodes at regular intervals, and asks them for data. It then stores the data in RRD-files, and (if needed) updates the graphs. One of the main goals has been ease of creating own "plugins" (graphs).
Installation:
edit Makefile.config
- create the user "munin"
- make install-main
- create a cron-entry to run "munin-cron" as the user "munin" every 5 minutes
- if you want to use the dynamic graphs, configure the cgi directory (an example for apache can be found in README-apache-cgi).