Free prevention software for linux

OSCache is a high performance J2EE caching solution that can cache portions of JSP pages, entire HTTP responses (including dynamically generated images), and arbitrary Java objects.
OpenSymphony Cache can provide your J2EE application with huge performance gains and graceful error tolerance (e.g., in the event of a DB failure, cached content is served).
Fast in-memory caching
OSCache allows you to execute dynamic content periodically (eg every 30 minutes) rather than every request and store the result in memory. Each further request is served directly from the memory cache, resulting in dramatic speed increases.
The cache is keyed programmatically. This means you can calculate a cache key that works for your situation. For example an ecommerce site might use product ID as keys, or content site might use an article date and article ID combination.
The cache is stored in standard scopes that any JSP programmer is familiar with (application or session). The session scope allows you to have different cached content per user. This is one unlike any other caching system weve ever seen.
Persistent on-disk caching
OSCache can also write the cache to disk. This provides caching across server restarts, and caching of datasets that do not fit into memory. Caching can be configured to use memory or file caching, or a combination of both.
If you want to persist the cache to somewhere other than disk, you can plug in a custom PersistenceListener. This allows you to persist the cache to anywhere (for example to a database via JDBC or to LDAP via JNDI).
When using both disk caching and memory caching. It is possible to limit the cache size to avoid using too much memory but let disk cache unlimited, resulting in browser style complementary disk cache. When cached objects are removed from memory, they are still on disk. If the item is needed again and it is not expired the cache file will be used. This also gives fault tolerance if the server crashes.
Persistence can also be switched to overflow mode using the property oscache.persistence.overflow.only. This changes the default behavior (of persisting every cache entry when there is a listener) to only persist when the memory cache capacity has been reached.
Excellent Performance
Written with performance in mind.
Mulitple cache requests can be handled concurrently.
Only one requesting thread needs to update an expired cache entry even if multiple threads are requesting it simultaneously. Other threads can be configured to either receive the recently-expired object, or block until the cached object is updated. Similarly, when a new entry is being added to the cache, other threads requesting that entry will block until it is ready rather than run off and race to build the same object. In a high load environment this can provide enormous performance benefits.
Automatically takes advantage of JRE 1.4 or higher if available.
Clustering support
OSCache can easily be configured to cluster across multiple boxes. This provides both scalability and failover support without any changes required in your caching code.
Flexible Caching System
OSCache allows you to cache portions of JSP pages, arbitrary Java objects, and even entire servlet responses.
Cache capacity can be set allowing you to limit the number of cached objects.
Multiple caching algorithms are supported such as LRU (Least Recently Used), FIFO (First In First Out), or unlimited. It is also possible to plug in your own custom algorithm.
You are given a huge amount of control over the way cached objects expire. Objects can be cached indefinitely, expired once they reach a certain age, or expired based on a cron expression. Programmatic flushing is also possible, and if that is still not enough pluggable RefreshPolicies allow custom refresh strategies.
Cached objects can be grouped together however you like, allowing for powerful management of cached data. This is an extremely useful feature that is far more powerful than what other caching solutions typically offer (such as the flushing of cache keys that match a particular pattern).
Fully event driven! OSCache fires events for various happenings under the hood such as cache entry events (adding, updating, flushing and removing) and cache accesses (hit, stale hit and miss). It is easy to add your own event handlers.
Multiple caches can be created, each with their own unique configuration.
Simple JSP Tag Library
The tag library to perform and control the caching is very simple. See the Tag Reference for more information.
Caching Filter
A Servlet 2.3 Filter allows for caching of entire pages and generated binary files (like dynamically created images or PDF files).
Comprehensive API
For the ultimate control, OSCache can be used through its straightforward API. You can instantiate, configure and control multiple caches programmatically. It would be possible for example to create one small in-memory cache that held currency conversion rates and was updated daily at 2am, while another cache could be purely disk based and used for holding dynamically created images.
Exception Handling
OSCache provides a way for your site to gracefully tolerate errors. This is not error prevention, rather if an error occurs it should not stop your site from functioning. For example if your database goes down, normally your product descriptions will not be browsable. Using OSCache you can cache those descriptions so you can still browse them.
Cache Flushing
Flushing of caches can be controlled via JSP Tags, so these functions can easily be built into your administration interface.
There is programmatic control over what caches are flushed (eg all caches or just a particular scope).
Cached objects can be expired in a number of ways. Objects can be told to expire once they reach a certain age, or, through the use of cron expressions, on particular dates and/or times (eg it is trivial to make an object expire every weekday at 3am). If this is not enough, you can expire objects programmatically as required, or plug in your own custom RefreshPolicy class that can dynamically decide when an object should be flushed.
Entire groups of objects can be easily flushed from the cache. For example suppose you were caching product data as well as entire pages of your website. When a product was updated, you could flush not just the product object but also all the pages that contain information about that product. No more waiting for the cached objects to expire before the updated content shows up on your site!
Portable caching
Pure Java, this means it is platform independent.
OSCache is compliant with Servlet 2.3 and JSP 1.2 standards, which means it should work in the latest generation of servlet containers and application servers.
i18n Aware
The caching is i18n aware and supports all encodings.
Solid Reputation
Thousands of downloads, hundreds of users on the mailing list.
Comprehensive JUnit test suite that covers every aspect of OSCache, including a web stress test and various concurrent cache access scenarios. To back this up, the kind folks at Cortex have supplied us with a Clover license to provide detailed code coverage analysis of our unit tests.
We have solid issue tracking using JIRA to keep track of any feature requests, bug reports and development progress. JIRA is provided courtesy of Atlassian.
Enhancements:
- CRON expressions to expire content at specific dates and/or times.
- Pluggable EntryRefreshPolicy.
- Reduced memory consumption.
- Faster disk persistence.
- DiskPersistenceListener deadlocks are avoided if a process has no rights to delete the cache file.
- There is a new JSP tag _addgroups_, and an interface to get a list of the cache event listeners.
- The commons collection dependency has been removed.
- Java 1.3 support has been dropped.

VXE protects UNIX servers from such intruders, hacker attacks from network and so on.
It protects software subsystems, such as: SMTP, POP, HTTP and any other subsystem, already installed on the server.
Main problem with UNIX security is that superuser can do with system anything he wants. There are programs (daemons) which work with superuser privilegies, for example popd, sendmail, and accessible from network (Internet/Intranet). There could be bugs in any program, so intruder connects to such programs via network, exploit existing bugs in it and get a control over all host.
VXE (Virtual eXecuting Environment) is an Intrusion Prevention System (IPS). It protects UNIX servers from intruders, hacker attacks from network and so on. It protects software subsystems, such as: SMTP, POP, HTTP and any other subsystem, already installed at the server. There is no need to change configuration of existing software - just PROTECT it.
So, VXE solve the following problem: protects host and particular subsystems, which work as superuser and can have bugs. This is the situation we have in real life.
VXE can be used for tasks such as:
daemon protection, as mentioned above;
provide user access to command line (shell, telnet) with restrictions (VXE describes - what tools and files are available for each user, and these restrictions cant be broken by any tricks); with VXE it is possible to allow user CGI hosting; VXE limits resources available to programs supplied by user, so it is painless to have user uploaded CGI scripts;
etc.
VXE source code is available under GPL license.
Enhancements:
- vsnprintf is used instead of vsprintf in print.c
- common.vxf fixed for two strings syscalls (like #38)
- in case of LISP error - arguments of syscall caused it will be printed in log
- web based VXED development system uses PERL instead of TclX & LISP

Packit (Packet toolkit) is a network auditing tool. Its value is derived from its ability to customize, inject, monitor, and manipulate IP traffic.
By allowing you to define (spoof) nearly all TCP, ICMP, IP, ARP, UDP, RARP, and Ethernet header options, Packit can be useful in testing firewalls, intrusion detection/prevention systems, port scanning, simulating network traffic, and general TCP/IP auditing. Packit is also an excellent tool for learning TCP/IP.
Packit 1.0 requires libnet 1.1.2 or greater as well as libpcap. It has been successfully compiled and tested to run on FreeBSD, NetBSD, OpenBSD, MacOS X and Linux.
Due to shifting priorities, this project is now in maintenance mode. If you find a bug, either submit a patch or email me the details. Ill do my best to put out fix in a reasonable amount of time.
Enhancements:
Injection:
- Bugfix NULL bytes in the payload (patch contributed by: Jason Copenhaver)
General:
- Updates to several build routines to support libnet 1.1.2+

NEsGUI is a peer-to-peer file sharing application written by Neill Miller in GTK+ which utilizes the NEshare library.NEsGUI is a Napster like application. Its one of the simplest and least creative applications utilizing the NEshare peer-to-peer file sharing library.
I started writing NEshare for many reasons. One reason is because I enjoy file sharing with others and I found that there were no true Free Software implementations or designs from the ground up. Thats one of the most important reasons to me personally, but I understand its probably not the reason youre reading this page. Second, I realized that most file sharing implementations that Ive played with simply DO NOT WORK well. The one implementation that worked *extremely* well for all of the time I participated in using it was Napster. As for the GnutellaNet (and the like), I tend to have problems with the decentralized nature. This is vague, I know. Specifically, they require an extraordinary amount of bandwidth as compared to a centralized counterpart such as Napster. They tend to generate a lot of garbage since they are responsible for tying themselves to a number of other nodes, which are likewise tying themselves to you. The *only* benefit that Ive realized with decentralized networks such as the GnutellaNet is the anonyminity involved. At best, you can see what IP address is downloading or uploading while the upload or download is occuring on your system. Beyond that, there is no record or trace of the transaction and does not involve user names which can be stored or screened, passwords which can be broken or stolen, or any form of user messaging or chat which is prone to SPAM or porn advertisments -- like the sad state of (the oldest widespread and possibly least recognized peer-to-peer system) IRC.
Another reason for writing NEshare is to help you realize that you should not be dependent on a corporation to dictate what you can and cant do with file sharing (a la Napster, FastTrack clients, or any other corporate owned network which you may have become attached to). For example, Napster allowed the sharing of digital music files. Where do you go if you are more interested in sharing original digital pieces of art amongst your friends? What about copies of an ever evolving digital document? Thus, I wanted to provide NEshare to you in case Napster or FastTrack or whatever you use suddenly becomes unavailable, or never suited your needs in the first place. Being Free Software, youre free to modify it and improve it under the terms of the GPL. And if you cant write code, call in a favor from a friend!
NEshare takes the best architectural ideas of centralized networks and mixes them with the best ideas of decentralized networks. It allows anonyminity since there is no messaging system, no username, no password and no record of you once youve left the network. It also works in a reliable manner (minus bugs!) because of the centralized nature. The basic method of transaction is similar to the familiar Napster and FastTrack clients. A user connects to an NEshare server and uploads a file list. The user can search and get results back from the server. Once the results are retrieved by the user, the user connects directly to another user for exchanging files. Thats the basic gist of the centralized approach, however the NEshare architecture is flexible and can work in a decentralized manner with relatively little modification if the benefits become more apparent.
One of the biggest advantages of a purely decentralized network (aside from the anonyminity aspect) is the fact that there is no central server which all users must rely on. In the world today, we see the prevention and the hindering of new technologies because big businesses fear to compete. This is wrong. Decentralized networks address this by not allowing a single entity to have complete control over a system. Thus, although threats can be made, they cannot be enforced against all users of a decentralized network. Contrast this with some centralized models - where a corporation takes control of an entire system. They are only pitting themselves against the giants and unfortunately they probably cannot win since (in recent U.S. history at least), Corporations (with cash) suppress our rights (Constitutional, fair rights, whatever) and dont ever look back. Look at the recent headlines regarding the RIAA and Hollywoods general reaction to Napster and other file sharing services. Everyone pounced on Napster and Napster did not survive. Sure, the company may still have a vision for itself, but everything that you and I enjoyed about the service is gone. The vision weve created for it is gone. I havent used Napster since late 2000.
Im not advocating using this software for actions which are questionably legal. Im providing this software for educational reasons because I believe that there is a lot to learn about networking applications and weve only seen the tip of the iceberg. This software has many legitimate uses such as online collaboration on any number of projects, sharing original works or documents, browsing which new Free Software packages are available amongst your peers, learning how a multi-threaded server works, learning how to use sockets, seeing an example of how a network protocol can be written from scratch, congesting your local network for bandwidth experiments and measurements, etc. The uses are endless. And the uses are legitimate. This software may help other to find something new. This software may *be* something new to others. Whatever the case, its all about vision.
By designing a Free Software implementation of a peer-to-peer protocol, Im offering it to you to suit your vision. I dont want to see one central server out there that everyone connects to for whatever use. I want to see the decentralization of the centralized model. I want to see something like what happened to the webserver to happen to NEshare. Each person that is interested in this kind of project should run and manage their own server for their own intranet. Choices are good. Although NEshare is centralized right now (like a webserver) -- wouldnt it be a horrible thing if all information on the web was hosted on the same server? This is what Napster tried to acomplish. They took the centralized server a little too far to prevent people like you and me from having our own visions and creative uses for the technology. NEshare should work differently. For example, if you look at streaming radio servers -- these are central servers all over the place which have several central resources (i.e. webpages) which tell you about which ones are available and their current status. This feature is planned for NEshare, although the first release of the server will have to be tracked manually if youd like to advertise your server to others.
Id like to add that I do believe that decentralized networks inherently have some cool ideas behind them, so I did not exclude the possibility of NEshare working in a fully decentralized manner. The first version that Im working on will be only centralized, but decentralization is an option since it should not prove to be too difficult given the architecture. However, since in my experience the fully decentralized network tends to have more issues than benefits, I would like to keep NEshare centralized. Again, a decentralization of the centralized model would be ideal.
The other major design goal of NEshare is to make it a toolkit. What I mean by this is that currently, there is a client library which can readily be dropped into an application of any kind. This means that for developers who are working on applications, if peer-to-peer file sharing would be useful, it can be easily used under the terms of the GPL inside of their own applications. This also makes for a more lightweight graphical user interface, since the bulk of the work is inside the client library. In order for all of NEshare to work in a purely decentralized manner, the work of the server must be integrated into the client library and a few new messages will need to be developed so that it can act as a servent. The architecture is rather flexible, and this will remain a design goal moving forward.
Needless to say this takes a lot of work. Im a single hacker at best and Ive been working on this project in free time since the summer of 2001. I can only do so much, and Im limited by my imagination and programming skills. Thats why I need your help. So far, my work consists of designing the networking protocol capable of accomplishing file sharing in a peer to peer manner, implementing this protocol in code, testing the code, improving the code, etc. I cant do this by myself (although unfortunately so far I have been and will continue to if no one volunteers). I would appreciate help in the areas of testing, documentation, and of course good old fashioned hacking. If this project sounds interesting to you, feel free to contact me.
Enhancements:
- Code now honors the std namespace so that its gcc-3.x compatible
- Fixed some event handling that caused erroneous message boxes to appear
- Better unexpected peer disconnection handling
- Added proper ChangeLog entries

Mailman is software to help manage email discussion lists, much like Majordomo and Smartmail. Unlike most similar products, Mailman gives each mailing list a web page, and allows users to subscribe, unsubscribe, etc. over the web.

Even the list manager can administer his or her list entirely from the web. Mailman also integrates most things people want to do with mailing lists, including archiving, mail-to-news gateways, integrated bounce handling, spam prevention, email-based admin commands, direct SMTP delivery (with fast bulk mailing), support for virtual domains, and more.

Nodezilla is basically an experimental grid based p2p system available for Windows and Linux (on Intel platforms).
Technically, Nodezilla is a secured, distributed and fault tolerant routing system (aka Grid Network). Its main purpose is to serve as a link for distributed services built on top of it (like chat, efficient video multicasting streaming, File Sharing, secured file store ...).
Nodezilla provides cache features; any server may create a local replica of any data object. These local replicas provide faster access and robustness to network partitions.
They also reduce network congestion by localizing access traffic. It is assumed that any server in the infrastructure may crash, leak information, or become compromised, therefore in order to ensure data protection, redundancy and cryptographic techniques are used.
Main features:
- Anonymous File sharing,
- Hierarchical Multimedia Streaming,
- Digital photo sharing with selected friends.
As this is a quite new and evolved p2p protocol compared to existing products, we welcome any comments on it.
Enhancements:
- Some crashes have been fixed, and there are routing fixes for relayed nodes.
- Performance has been tuned.
- This release uses new features of Vista for services rights restriction and buffer overflow prevention.

ClarkConnect is a powerful yet easy-to-use software package that transforms off-the-shelf server hardware into a dedicated Internet firewall, gateway or server.
ClarkConnect is a great solution for schools, businesses, organizations, and home offices.
ClarkConnect transforms standard PC hardware into either:
- a dedicated firewall/gateway for your network, or
- a standalone server on your local network
The award-winning Linux-based solution includes firewall and security tools, along with file, print, web, e-mail, proxy, antivirus, antispam, content filtering, VPN servers and more. A detailed feature list is shown in the sidebar below.
Easy to Install and Manage
The software is easy to install on off-the-shelf hardware ... you can be up and running in minutes.
- purchase a CD, or download burn your own
- insert the CD into the server system
- start the server from the CD
- follow the installation wizard
Once you have your ClarkConnect system up and running, you can configure the server/gateway with an easy-to-use web-based administration tool.
Integrated Updates and Managed Services
- ClarkConnect includes integrated Gateway Services (GS). to update, manage and monitor your system.
- 24/7 port and resource monitoring
- DNS services, including dynamic DNS
- antivirus protection
- antispam tools
- content filter updates
- managed/dynamic VPN
- daily security audits
- intrusion detection updates
- e-mail/MX backup
Different Needs... Different Solutions
We offer three different editions of the ClarkConnect software. Each edition solves different needs.
Professional Edition - Firewall and Gateway
The Professional Edition is a firewall solution that protects your network from the constant hazards lurking on the Internet. The software includes a stateful firewall, antispam protection, antivirus protection, content filtering, managed VPN, intrusion prevention, and more.
Office Edition - All-in-One Gateway/Server
The Office Edition includes not only the core security features found in the Professional Edition, but also server features: file server, print server, web server, advanced mail server, and database server.
Home Edition - Home and Hobbyist Solution
The Home Edition is designed for home use -- we include extras such as MP3 support, online photo albums and computer security model appropriate for a home environment.
Main features:
- IPsec VPN
- PPTP VPN
- Managed/Dynamic VPN
- 1-to-1 NAT support
- DMZ support
- Stateful Firewall
- Intrusion detection
- Intrusion prevention
- Antispam
- Antivirus (license req.)
- SMTP authentication
- SMTP gateway
- SMTP server
- POP and IMAP servers
- Webmail
- Banner ad blocking
- Web proxy
- Content filtering
- Bandwidth manager
- DSL (including PPPoE)
- Cable Modem
- 802.11b Wireless
- Internal DHCP server
- Caching DNS server
- Hardware and Software RAID
- multi-processor support
- Web-based configuration
- Optional Webmin package
- Apache web server
- Support for CGI and PHP
- Secure/SSL support
- FTP server
- Windows file server
- AppleShare file server
- Print server support
- Printer sharing
- MySQL Database
Whats New in 4.1 Stable Release:
- File server antivirus; Samba PDC (Primary Domain Controller) support; improved server and LAN backup features; new greylist and blacklist support for the antispam engine; greylist antispam engine; e-mail disclaimer; e-mail virtual domain support; e-mail catch-all mailbox support; webmail administration tools; the backup and restore system settings now includes the user database; the firewall has changed to accommodate the new Hot LAN and Blocking features...
Whats New in 4.2 Alpha 1 Development Release:
- ClarkConnect Community 4.2 Alpha 1 is available. Though it has only been four months since the last release, version 4.2 brings quite a few new features. This alpha build is intended for developers, integrators and curious users. Typical uses for this alpha build: final integration testing for third party developers; testing new hardware and drivers with the Linux 2.6.18 kernel; getting a sneak preview of the upcoming 4.2 release. This is alpha software, so quite a few software modules are still incomplete or not well tested. The most important known issues are: Webconfig template graphics and icons are incomplete; graphical console tool does not display on the screen properly....