Free sentinel software for linux

Download Sentinel++ is an Anti-leech, download limiter / file manager, that uses tokens to verify downloads instead of HTTP_REFERER or IP which can be spoofed or changed.
The install is as painless as possible with only one file to upload and execute. The install automatically creates the sub-directories and files, all you need to do is follow the on-screen instructions for permissions.
Security has been the focus throughout development, even the install program is built on the latest recomendations for security. Logging is done with text files and can have errors and alerts sent via email or stored in a txt file.
Downloads can be limited to a certain transfer size per time frame, which can be further broken down into smaller intervals, all with only a couple settings. This helps spread out the limitation to different timezone and prevents all available bandwidth being used in a short period
Main features:
- Completely free (free as in speech);
- Multiple language capability (all text is in config file, no hardcoded messages);
- Download counter file;
- xhtml/css compliant message output, fully customizable;
- Install script for easy setup;
- All user supplied input securely handled;
- Uses tokens to validate download requests. A superior method than .htaccess or http_referer which can be spoofed or limit users with firewalls;
- Tokens are good for a day by default, but can be set to expire at any time in 1 minute increments;
- A log is kept of invalid token attempts and information on tracking down the source;
- All errors and warnings can be written to a log file or sent to an email address;
- Supports unlimited directory structure of downloadable files (no need to specify where a file is located);
- Option to turn off bandwidth protection;
- Option to turn off any error/log report;
- Robust error handling;
- Ability to specify the total amount of transfer (bandwidth) allowed, over the total amount of time;
- Ability to specify interval lengths for download cut-off so all the allowed bandwidth does not go to one time zone / day /hour;
- Ability to put in a ratio of download clicks to actual bandwidth used;
- Log of all download details kept;
- Download log can be auto-archived;
- Ability to specify the download log size before archive;
- Ability to specify the download archive size before deleting;
- Ability to have a warning issued (email or log file) about the archive file reaching its maximum;
- Download count can be tracked in a Mysql database;
- Flood control on user clicks. Ability to set the number of times a user can click on a link in a given interval;
- Ability to allow specific offsite downloads via tokens;
- Pre-made example download page that is xhtml/css compliant;
- Pre-made file manager that displays all files, directories, sizes, downloads, dates, authors and descriptions for each file
- Ability to deny link sharing between browsers.
- Alternative install locations for secure files
- Logs automatically rotated, no on-going maintenance
- Ability to have multiple files with the same name
- Turn-Key install operation. Ready to begin secure downloads in 5 minutes or less;

SimCList project is a high quality C library for handling lists.
SimCList is available for free, under restrictions imposed by the BSD license.
SimCList API is good because:
- it is simple, yet powerful
- it makes elegant and consistent use of information hiding
- it abstracts the actual data type to store
- it is fairly total
The library itself is very performant and makes a good compromise between performance in terms of time and space:
- insertion is O(n) [typically n/8]
- extraction and deletion are O(n) [typically n/8]
- iteration is O(1)
- sorting is always O(n logn), without worst case
Thread safety
The SimCList library is thread safe, meaning that many threads can run SimCList operators on different lists concurrently without hurt, or also read operations on the same list.
However, of course, no safety guarantee is made for performing concurrently write+write or read+write operations on the same list (eg: insertion, deletion, sorting, ...). For performance and portability reasons, protecting such operations from concurrency is left to the library adopter.
Performance
SimCList has been designed with ease to use and performance in mind. There is some example factors that have been taken into account, and against which the code has been optimized when implementing SimCList:
- overhead of function calls
- cache locality
- number of branches, possible CPU stalls or pipeline flushes
- dynamic memory allocation weight on the OS
- other mathematic/probabilistic optimizations for avoiding worst-case or improving average case behaviours in algorithms
Many parts of SimCLists code have been deeply improved with profiling analysis.
Enhancements:
- Transparent inclusion in C++ applications is natively supported.
- Sentinels are used to improve performance on list traversals.
- A problem was fixed with list_insert_at, which could output inconsistent lists when inserting into even-sized lists in position 0.

Template::Plugin::XML::DOM is a plugin interface to XML::DOM.

SYNOPSIS

# load plugin
[% USE dom = XML.DOM %]

# also provide XML::Parser options
[% USE dom = XML.DOM(ProtocolEncoding = ISO-8859-1) %]

# parse an XML file
[% doc = dom.parse(filename) %]
[% doc = dom.parse(file = filename) %]

# parse XML text
[% doc = dom.parse(xmltext) %]
[% doc = dom.parse(text = xmltext) %]

# call any XML::DOM methods on document/element nodes
[% FOREACH node = doc.getElementsByTagName(report) %]
* [% node.getAttribute(title) %] # or [% node.title %]
[% END %]

# define VIEW to present node(s)
[% VIEW report notfound=xmlstring %]
# handler block for a ... element
[% BLOCK report %]
[% item.content(view) %]
[% END %]

# handler block for a ... element
[% BLOCK section %]
< h1 >[% item.title %]< /h1 >
[% item.content(view) %]
[% END %]

# default template block converts item to string
[% BLOCK xmlstring; item.toString; END %]

# block to generate simple text
[% BLOCK text; item; END %]
[% END %]

# now present node (and children) via view
[% report.print(node) %]

# or print node content via view
[% node.content(report) %]

# following methods are soon to be deprecated in favour of views
[% node.toTemplate %]
[% node.childrenToTemplate %]

This is a Template Toolkit plugin interfacing to the XML::DOM module. The plugin loads the XML::DOM module and creates an XML::DOM::Parser object which is stored internally. The parse() method can then be called on the plugin to parse an XML stream into a DOM document.

[% USE dom = XML.DOM %]
[% doc = dom.parse(/tmp/myxmlfile) %]

The XML::DOM plugin object (i.e. dom in these examples) acts as a sentinel for the documents it creates (doc and any others). When the plugin object goes out of scope at the end of the current template, it will automatically call dispose() on any documents that it has created. Note that if you dispose of the the plugin object before the end of the block (i.e. by assigning a new value to the dom variable) then the documents will also be disposed at that point and should not be used thereafter.

[% USE dom = XML.DOM %]
[% doc = dom.parse(/tmp/myfile) %]
[% dom = new value %] # releases XML.DOM plugin and calls
# dispose() on doc, so dont use it!

The plugin constructor will also accept configuration options destined for the XML::Parser object:

[% USE dom = XML.DOM(ProtocolEncoding = ISO-8859-1) %]

Arnos IPTABLES firewall script was initially written because I needed to protect my single-homed Linux machine at work. I wrote it at the time I couldnt find any script that really satisfied my needs except for one that was written by a guy called Seven.
I helped him for several months with the work on his script by suppling patches, reporting bugs etc. In this period I was fortunately also able to master scripting for iptables myself because soon Seven discontinued his work, I never got to even talk to the guy ever again. At that point I decided to continue his work, or actually I started my own branch based on his script.
In the summer of 2002 I finally got an ADSL connection at home. Initially I used the iptables firewall that came with the great ADSL4LINUX-package (http://www.adsl4linux.nl). But it didnt take me long to come to the conclusion that their iptables firewall lacked important features like port-forwarding and flexbility with "trusted hosts" etc.
I also didnt like the fact that I had to use a different firewall for my home machine and the machine at work. This made me decide to use some of the ADSL4LINUX knowledge to implement ADSL support.
By now (about 1 year later as of writing) there are only few remnants left of Sevens original script and many, many, many improvements were applied. One major improvement is the ADSL and NAT support (Check the features page with the specifiations of my firewall). For version 2 (alpha) I plan to completely rewrite to script to make it more flexible and to increase the usability for others.
Main features:
- Very secure stateful filtering firewall
- Both kernel 2.4 & 2.6 support
- It can be used for both single- and multi(eg. dual)-homed boxes
- Masquerading (NAT) and SNAT support
- Multiple external (internet) interfaces
- Support multiroute NAT & SNAT (load balancing over multiple (internet) interfaces)
- Port forwarding (NAT)
- Support MAC address filtering
- Support for DSL/ADSL modems
- Support for PPPoE, PPPoA and bridging modem setups
- Support for static and ISP assigned (DHCP) IPs
- Support for (transparent) proxies
- Full support for DMZs and DMZ-2-LAN forwarding. You can also use it to isolate your eg. wireless LAN.
- (Nmap)(stealth) portscan detection
- Protection against SYN-flooding (DoS attacks)
- Protection against ICMP-flooding (DoS attacks)
- Extensive user-definable logging with rate limiting to prevent log flooding
- Includes options to optimize your throughput
- User definable open ports, closed ports, trusted hosts, blocked hosts etc.
- Log & protection options are both highly customizable
- Support for custom iptables rules in a seperate file
- It can be used with chkconfig runlevel system (eg. RedHat/Fedora)
- Main focus on TCP/UDP/ICMP but additional support for *ALL* IP protocols
- It works with Freeswan IPSEC (VPN) & SSH Sentinel (http://www.freeswan.org) (+virtual IPs)
- It works with PoPTop PPTP (http://www.poptop.org)
- It works with UPnP
- DRDOS protection/detection (experimental)
- Its easy to configure
- And much more.
Enhancements:
- This release fixes a nasty bug in the NAT forwarding rules that caused using subnet-source-restrictions not to work.
- It adds an extra rule to the DHCP server section to allow packets from DHCP servers in the same segment.
- There are several plugin updates.
- A Racoon IPSEC VPN plugin and a transparent DNAT plugin have been added.