Free limewire p2p file sharing software for linux

MUTE File Sharing is a peer-to-peer network that provides easy search-and-download functionality while also protecting your privacy.
It compiles as a fast, native application for many platforms (no Java, no Python, etc.).
MUTE protects your privacy by avoiding direct connections with your sharing partners in the network. Most other file sharing programs use direct connections to download or upload, making your identity available to spies from the RIAA and other unscrupulous organizations.
MUTE is based on research, and experiments show that it works quite well. MUTEs ant-inspired routing is light-weight, robust, and adaptive. Results from experiments in real MUTE networks show that the collective behavior of MUTE nodes quickly finds the shortest (or fastest) routing path between two nodes on the network.
Enhancements:
- This release fixes bugs in MUTEs initial connection to the network upon startup.
- MUTE has also been upgraded to Crypto++ 5.4, so it should now compile using GCC 4.1.

Web Sharing is a small tray applet for sharing files on the web.

Publish anything on the Internet or your local area network at home, office or school from a folder on your hard disk with just a few clicks of a mouse!

Real-Time Proactive Secret Sharing Library is an implementation of the Shamirs secret sharing scheme and Herzbergs proactive secret sharing algorithm.

Real-Time Proactive Secret Sharing Library targets the RTAI OS. It includes a port of GNU GMP to RTAI, which is used for multiple precision arithmetic operations.

to run the rt-pss

./start_pss ID (*) ID should be between 0 and PSSW_NUMBER_OF_MACHINES-1(this constant is defined in src/share_app_pssw.h)
(*) each local RT-PSS should be executed with a
different ID starting with 0
(*) you must have superuser privilegies to do that.

to stop the rt-pss


./stop_pss (*) be sure that no applications that uses the RT-PSS are
running.
(*) you must have superuser privilegies to do that.

developing RT-PSS Apps

There is a demo application available in the directory: examples/GetShare. The RT-PSS API can be consulted in the file README.API

Shezhu Resource Sharing System project is an application for scheduling and booking shared resources such as rooms and equipment.
The client only needs a modern Web browser.
It has a user friendly point and click interface, visual filters for making block/repeat bookings, concurrent users and double booking prevention, allows local site customization, and supports configurable academic term/semester blocks.
Main features:
- Portable - client only needs a modern web browser
- Point and Click - almost no typing required
- Intuitive - simple, obvious, consistent and user friendly
- Innovative - visual filters for making block/repeat bookings
- Powerful - concurrent users and double booking prevention
- Configurable - local site customization supported
- Useful - built in support for configurable academic term, semester and session blocks
- Free!
Requirements
In order to run or build the Shezhu Resource Sharing System you need some third-party software available on your machine.
Client
The client needs a modern web browser and the best browsers for this application are Firefox, Mozilla (including the Netscape branded equivalent and Gecko derivatives such as Galeon) and Microsoft Internet Explorer. The newest versions of all these browsers will work best. This application also works with the Konqueror and Opera browsers but these have some issues which may affect functionality. All browsers need JavaScript enabled. Any of these browsers may not work properly (or at all) depending on the operating system they are running under. Text based browsers (such as Lynx) are not supported.
For a comprehensive list of supported client browsers and operating systems refer to this browser compatibility chart from the most recent release of the application.
Server
The server needs recent versions of the Apache web server and the MySQL database server.
The server has only been tested on Redhat9 and FedoraCore3 Linux/i386 platforms although there is no specific reason why it should not work on other Linux platforms and distributions.
Development
Rebuilding this application from source requires a standard Unix development environment with the sh, make, cc, cpp, sed and awk utilities. Also required are RCS, Perl (5.6+) and the ImageMagick program. Also required is RPM to build a distribution. All these programs would probably come as standard in Linux distributions, other platforms may not have all of them by default.
Enhancements:
- This release adds support for Apache2 and multi-site installations, internal restructuring, a better installation tree, and improved access control management.

FrostWire is a community driven project based on source code released by LimeWire LLC to create and maintain a Gnutella client according to the open standards of an international community.

We are busy building a website and creating a new design for the FrostWire Gnutella client. Since LimeWire is a registered trademark we cannot distribute the client under its old name.

For that reason, we are looking for creative p2p fans that would like to create skins, design logos or websites. However we are also trying to get more people working on the Java core, the interface and the C++ windows installer (based on GnucDNA and NSIS). If you are interested in maintaining LimeWires legacy get involved!

We are trying to maintain good relations to the LimeWire project. The FrostWire team (all of whom are still members of the LimeWire open-source community) regrets LimeWires decision to start filtering content on Gnutella.

However, we will continue supporting LimeWire development and do not wish to make fundamental changes to the LimeWire core itself. FrostWire will not break with LimeWires design philosophy.

However the FrostWire project will never offer a PRO version. The FrostWire project will always remain strictly non-profit and free of any bundled software, including any ads or nags.

file*HANDLER project is primarily a Perl script which coordinates some free media conversion packages (cited later) with a PostgreSQL back end accessing server to index and serve binary and text files direct from the database. A simple CGI file with embedded AJAX makes calls to this server which is also constantly looking for other alive f*H servers on the Internet.
Since the server caches media into the SQL database on demand, as the network grows, the network improves.
Its gridded directory sharing/browsing/searching with streaming audio/video as well as flat text/doc/pdf/image display for everyone. Its written with a few hooks for tags that would be included in your actual front page so that the UI is discard-able -- anyone can quickly rewrite a whole new [GT]UI without having to worry about the syntax of the newest version of dojo.licio.r or whatever.
If you wanted to ignore the JS/HTML/CSS hooks then you can easily use the system to make direct requests that just return lists formatted as HTML table-bodies. In other words, the markup IS the markup.
As such, Ive whipped up a Dojo 0.2 Widget that coordinates the serving backend with a UI so anyone can embed f*H functionality anywhere, or easily customize a provided default page.
A file*HANDLER server is really a few constituent parts Ive tied up for you (top down):
- A local web page providing the UI(served by an HTTP server of your choice) that is generated by a cgi script with embedded AJAX.
- A secondary portion of the same CGI script, acting as middle-ware, which communicates, via AJAX, with the local front page to reconcile asynchronous JavaScript requests with the file*HANDLER sub-network back-end.
- An always-on network server written in PERL that serves to the front and end communicates laterally with everyone elses file*HANDLER back-end PERL server additionally, it manages indexing of content directories you choose to serve.
- A PostgreSQL database that is accessed only via internal PERL routines called from your front page.
So for example, a remote user comes to your site. First, not only can they browse and search your files, but they can also browse and search the files of anyone else hosting a file*HANDLER server that your local server knows about. (file*HANDLER identifies other servers on the network automatically). The user can now read/view/listen/watch by stream any content they find from whomevers server. Theres no download, so theres so actual sharing, just direct streaming to the users browser.

iptables-p2p is an iptables match module capable of matching various peer-to-peer networks. It works by examining the application-layer protocol.
This is how you install iptables-p2p:
1. Copy the iptables headers to an appropriate place (/usr/include) or install the iptables-dev package if your distro has one. (see Installing iptables headers)
2. Run make in order to compile iptables-p2p.
3. Insert the kernel/ipt_p2p.o module directly using insmod or copy it into your modules directory. If you are using a 2.6 kernel, the module is named kernel/ipt_p2p.ko.
4. Insert the iptables library libipt_p2p.so into the iptables lib directory (usually /lib/iptables).
Enhancements:
- 0.3.0a
- Fixed iptables-save/iptables-restore
- Fixed module versioning support