Free bluetooth protocol stack software for linux

KDE Bluetooth Framework is a set of tools built on top of Linux Bluetooth stack BlueZ.
Our goal is to provide easy access to the most common Bluetooth profiles and to make data exchange with Bluetooth enabled phones and PDAs as straightforward as possible.
Enhancements:
- Exporting public includes to make other applications use of kdebluetooth.
- Fixed some bugs on kioslaves.
- Fixed kbluepin.
- Allow compiling with lastest openobex and bluez packages.
- Fixed compilation with gcc >= 4.1.
- Fixed configure script, warning user about missing headers.

Ethics Search Protocol in short ESP is an XML-based protocol for search engines that is designed to allow people to express specific ethical requirements when performing searches.
Consumers seldom get the chance to communicate ethical requirements because the proper communication channel does not exist. This project has the goal to offer an open source specification and implementation for that missing communication channel.
Enhancements:
- Changes were made to Category, OrganizationSearchParameters, SearchProfile, and Community.
- PolicyReference complements PolicyStatement.
- EvaluationScheme complements VotingScheme.
- The Envelope type was removed.
- The documentation was improved.

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.

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.

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

Whamb Sharing Protocol Daemon (WSD) is a perl script that allows you to share MP3 or OGG on a Unix/Linux or windows system.WSD needs perl 5.7.3 or later (5.8.0 recommended) and some modules (HTML::Entities, Encode, MP3::Info), you will find any instructions you need in the readme, so please read it ! WSD also needs RendezVous from Apple, its opensource and runs on lots of platform including linux/*BSD/Windows/Solaris and all Posix OSes

Installation is simple but depends by your operating system:
make os=linux on linux
make os=opensd on openbsd
make os=osx on macosx
make os=solaris on solaris

if you are running NetBSD or FreeBSD edit the makefile you will see:
ifeq ($(os),openbsd)
CFLAGS_OS = -DHAVE_SOCKADDR_SA_LEN -DHAVE_DAEMON -DHAVE_SOCKLEN_T -DHAVE_BROKEN_RECVDSTADDR
change it to
ifeq ($(os),bsd)
CFLAGS_OS = -DHAVE_SOCKADDR_SA_LEN -DHAVE_DAEMON -DHAVE_SOCKLEN_T

and use make os=bsd

You can start it with something like: build/mDNSResponderPosix -n "`hostname`" -t _whamb._tcp. -p 7603 -d
You may also want to copy mDNSResponderPosix to your /usr/bin directory

Very Simple Control Protocol Daemon is a daemon for home automation tasks.
VSCP protocol is a very simple and free protocol for SOHO automation tasks & friends. The protocol is so easy that everyone can grasp the idea behind it in a few minutes.
Therefore its also very easy to construct and use VSCP aware modules and components. Nodes just start up and then serve the control solution reliable and stable for ever and ever and ever.
The protocol is free and is not designed to conquer the world and every Small Office and HOme. Very Simple Control Protocol Daemon is constructed just because its fun to make tiny little things work together.
Enhancements:
- The port was changed from 1681 to the IANA registered 9598. Scripts for Digitemp support and the first version of the ODIN database were added.