Free protocols software for linux

SurgeMail is the fastest, most robust and secure, full-featured email server on the market today supporting all the protocols and standards. Surgewall works with every mail server and can be installed in minutes, instantly gives you the uniquely advanced, Spam Blocking, Virus Scanning and even user configurable filtering and friends modes normally only found in our SurgeMail product.
Main features:
- User existence is checked at rcpt stage to prevent major spam problems
- Spam and virus free email
- Friends mail screening system.
- Integrated mail server and web based email
- Web based administration (user, domain and server)
- Full SSL secure support for all protocols
- Runs on platform of choice (Windows, most Unix versions)
- Installs in minutes and unparalleled after sales service

TAHI Test Suite provides a mechanism for validating an IPv6 implementation against a standardized test for conformance to the IPv6 specification, extensions and directly related protocols.
Enhancements:
- Ported FreeBSD-4.x
- Dont support FreeBSD 2.x
- pa can decode MIP6 packets
- All interoperability test tools is included.

FSP stands for File Service Protocol. It is a very lightweight UDP based protocol for transferring files.
FSP has many benefits over FTP, mainly for running anonymous archives. FSP protocol is valuable in all kinds of environments because it is one of the only TCP/IP protocols that is not aggressive about bandwidth, while still being sufficiently fault tolerant.
FSP is what anonymous FTP *should* be.
FSP: reliable and bandwidth friendly way to access publicly available data. Some people calls it UDP FTP.
Enhancements:
- use getopt from stdio.h instead of getopt.h in fspscan.c
- fspscan now compiles on AIX and other OS without glibc (hoaxter)
- !! fixed fatal bug from b23. Server sends large packets to clients if
- client request has not prefered reply size inside. This confuses all old fsp clients.
- common/strdup.c removed
- bsd_src/function.c bcopy -> memmove
- removed STDC_HEADER checks, drop support for pre-ANSI compilers started work on alternate SCons based build system
- fspd: use urandom, not random -> avoid hangs on Lin suck 2.6
- build system converted to SCons
- !! fixed directory listing bug in client library introduced in beta23
- improvements to security of FSP clients
- seq. numbers are now randomized
- seed random number generator in fsp clients
- check cmd in received packets
- check pos in received packets

Generic Protocol Framework aims to allow users to rapidly prototype different emerging communications protocols. Implementations can be easily "dropped in" and tested independant of a finished product. Testing on both the end product, and the protocol itself can be easily accomplished. The tool aims to provide the developer and end user with a robust solution which can track the size of messages, how rapidly they will be generated, and how many of each type can be seen.
Why the GPF:
There are many similar tools available. The problem with many of these tools is that they are 1) closed source, 2) not easily adaptable to a specific implementation (they use custom languages), 3) expensive. The advantages of the GPF are its open source nature, the ease of which it can be adapted, and the cost: free!
Basic Flow:
Modification of the GPF is fairly simple. Tool-opts.h contains the basic options that will be applied to the packet while it is being built. To transmit a packet, the system calls the tx_message() function, and passes the message ID as well as the option block. This is then passed to the custom function: tx_message_custom() in tx.c. From the message id, the system selects an appropriate tx_* function (to be implemented by the user) and passes an unsigned char **, where the buffer will be written, and the option block. In turn, that function will make heavy use of the add_buf_tu*() functions, which will allow the user to add a tubyte8, tuint16, or tuint32 number to the buffer.
In daemonize mode, the basic options are set, and the system then listens for incomming packets. When a packet arrives, the system calls basic_parse() on the packet. This function then calls basic_parse_custom(), found in parse.c. In turn, this can call any appropriate parsing helpers, including the get_tu*() functions, which allow the user to retrieve a tubyte8, tuint16, or tuint32 from the buffer. CAVEAT: if the first two bytes of the buffer are zerod, it will be treated as an END message. However, recovery is available. In the basic_parse_custom() message, you can set the end_signal_caught variable of the option_block to 0. In this case, it will not stop the daemon from running.
Enhancements:
- Currently, TCP support is somewhat experimental.
- Testing for that portion will be ongoing.
- No clear examples are provided.
- The examples/ directory contains the precursors to a MIP example.

Bio::MAGE::Protocol::Software - Software represents the software used.

SYNOPSIS

use Bio::MAGE::Protocol::Software;

# creating an empty instance
my $software = Bio::MAGE::Protocol::Software->new();

# creating an already populated instance
my $software = Bio::MAGE::Protocol::Software->new(softwareManufacturers=>$softwareManufacturers_value,
softwares=>$softwares_value,
hardware=>$hardware_value,
type=>$type_value);

# setting and retrieving object associations
my $softwareManufacturers_val = $software->softwareManufacturers();
$software->softwareManufacturers($value);

my $softwares_val = $software->softwares();
$software->softwares($value);

my $hardware_val = $software->hardware();
$software->hardware($value);

my $type_val = $software->type();
$software->type($value);

ZRTP Protocol Library is an implementation of Phil Zimmermanns ZRTP protocol, created based on and interoperable with Zfone beta 2.

Using this package, together with GNU ccrtp (1.5.0 or later) provides a zrtp implimentation that can be directly embedded into client and server applications, rather than the overhead penalty of using an external proxy such as zphone. The first application to demonstrate this capability is the 0.8.2 release of the Twinkle softphone client.

Please note, this library is licensed under the GNU GPL, version 2 or later, and has been copyright assigned to the Free Software Foundation.

The HTTP Time Protocl (HTP) system is a set of utilities to set and maintain the system clock from the HTTP/1.1 (RFC 2616) "Date:" header. HTP requires Libconfig.
The purpose of HTP is provide a simple to use system that can be used on any system that is connected to the internet and can access atleast one web page (either directly or through a proxy) to be able to maintain an accurate clock.
HTTP Time Protocol uses basic statistical analysis to arrive at the most accurate time possible given enough servers. The more servers HTP is configured to use the more accurate the clock can be.
Enhancements:
- Cleanup/simplification of the code.
- A more robust implementation of the "-p" (precision) switch.

AMI provides a full P2P network.

AMI is a universal P2P framework written in Java and XML. It allows people to communicate using plug-in AMI protocols. It can support any P2P protocol.