Free share computer files with anyone software for linux

Computer Breaker project is a network testing tool for services vulnerabilities.

Computer Breaker is a network testing tool that allows networking administrators to test if a computer is vulnerable to malicious attacks.

Using the Nessus scanner, computer-breaker scans the remote host and automatically exploits its vulnerabilities.

G-Share is a PHP script that allows you to share your Gmail attachments with the world, it is a download center with files stored in your gmail account.

G-Share project uses a MySQL database to store important data such as categories, download count, visitors, gmail accounts, etc...

list files package prints to file list of files in a given directory.
Handy if youd like to, say, tell a friend of yours what ebooks you have, and wouldnt feel like typing them all by hand.
Hope you can find it useful.
INSTALLATION
i assume youve got everything in its standard places; otherwise you probably know what to do anyway.
to install for one user
copy listFiles.desktop to ~/.kde/share/apps/konqueror/servicemenus
copy listFiles.sh to /usr/local/bin or elsewhere in the path
to install for all users
copy listFiles.desktop to /usr/share/apps/konqueror/servicemenus
copy listFiles.sh to /usr/local/bin or elsewhere in the path
Enhancements:
- added counting the number of items
- added the possibility to change the place where the listing is written to
- some minor changes to the code

Computer History Graphing Project is a computer family tree.

The Computer History Graphing Project is an attempt to graph every computer standard, every piece of hardware, every OS, and every computer language in one big family tree.

Non-Networked File System provides a consistent file system over several non networked UNIX computers (or slow networked). For example on your computer at home and at work using only a floppy disk for the synchronisation.
Main features:
- You are sure to work on the latest version of files.
- You dont need to remember which files are modified on an host and must be transfered on others.
- You dont need to made backup, because if a computer crash the file system is still on the other computers working with NNFS.
- The NNFS medium is choosen by a user shell script, it could be: floppy disk, usb key, serial connection, ...
- Minimal NNFS medium bandwidth to make the updates.
- EASY TO USE: Running ``nnfs command before and after your work.
- Numbered backup of files modified/deleted on NNFS.
- If you modify the same file on several hosts NNFS solves the update conflict.
- The program has been hugely tested.
Enhancements:
- This release fixes the case where the user modifies a file mode while NNFS is running and NNFS is configured in order that a file mode change does not imply file synchronization.

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.