Free 2.2.4 software for linux

ArX is a Revision Control System (RCS), like CVS, Subversion, or GNU arch. It manages "archives" (collections of files), such as source code files for a software project.
ArX tracks the history of each file, along with change comments, version tags, forks and branches, etc. It can store files and documents of any kind, but the largest benefits are with text files, rather than binary files.
Main features:
- Ease of learning and use
- Powerful branching and merging features
- Speed, even when working with large repositories
- Effective distributed development
- Friendly and helpful user and developer communities
- Cryptographic data integrity features
- Ability to publish archives on almost any server
- Portability to multiple operating systems (still in progress)
Like CVS (and most modern RCS tools), ArX uses an "optimistic" locking model, which allows multiple developers to modify the same file at the same time, and then resolves any conflicts as each developer checks in his or her work. While this may sound scary if you are used to systems that "lock" files, it actually works very well, as confirmed by the thousands of projects that have used this approach (in CVS) for many years.
Unlike CVS and most traditional RCS tools, ArX is "distributed", which means that ArX does not require a central server. Each developer can maintain their own "archive" of their projects, but can easily share their work with other developers. This modern design works well with teams that are geographically distributed, and especially with teams where some contributors are not part of the core team.
ArX includes an optional patch queue manager to enable centralized, CVS-style, development when desired. ArX differs from many of the newer distributed SCM tools in that it does not require every working tree to contain an entire copy of the archive history.
Each archive can store multiple branches, each of which could be checked out in multiple working trees. Other tools may use the terms "patch pooling" or "centralized storage" for this type of feature, and it is important for efficient branching on systems without hardlinks. Also, ArX archives can link to other archives (including remote archives) for older history, allowing branches of remote projects to be very small and fast.
Another important feature of ArX is that an archive can be published on any HTTP web server. It does not require any special code running on the server, which has some significant advantages: First, it allows projects to host their code on almost any inexpensive web site, including the free personal home pages offered by many ISPs. Second, it keeps the server very secure, because the only service required is a standard web server such as Apache or Boa.
Enhancements:
- ArX now uses three-way merging as a default, and supports third party merge tools.
- ArX is also much more clever about renames.
- "merge" now uses the --update option instead of using heuristics.
- ArX now records when there are conflicts in the tree, and will not let you commit unless they are resolved.
- ArX now uses -v and -q for verbosity.
- "commit" now supports --author and --date options for Tailor.
- The patch queue manager has been updated, and some small bugs were fixed.

NuFW is an enterprise grade firewall that performs an authentication of every single connection passing through the IP filter, by transparently requesting user?s credentials before any filtering decision is taken.
Practically, this means security policies can integrate with the users directory, and bring the notion of user ID down to the IP layers.
Main features:
- Authenticate any connection that goes through your gateway or only from/to a chosen subset or a specific protocol.
- Perform accounting, routing and quality of service based on users and not simply on IPs.
- Filter packets with criterium such as application and OS used by distant users.
- Be the key of a secure and simple Single Sign On system.
- Scalable : NuFW is composed of two daemons that can be put on different systems and the main daemon is heavily multithreaded.
- Modular : User authentication and Access control list verification are performed via loadable module (system, ldap, dbm, plaintext modules are provided). User activity logging can be done via syslog, mysql or postgresql.
- Open : NuFW is released under the GNU GPL licence v2 and all protocols are fully documented.
Enhancements:
- This release fixes a security issue related to time-based filtering rules.
- A regression was leading packets not to be dropped when their arrival time was out of period.
- It also features some improvements and bugfixes.

Acmemail is a multiuser IMAP/POP3 to Web gateway (or webmail program). It reads mail from a mail server and displays it using HTML on a web server. It is written in Perl, has full support for MIME (and mod_perl) and is quite pretty.
This program has support for MIME, is written in Perl and is very pretty.
Enhancements:
- Fix for mkdir problem BSD/OS 4.2. Patch from A.Lalev
- Fixing a nasty CSS vulnerability. Basically it was possible for somebody to run JavaScript code like this: http://yourdomain/cgi-bin/acmemail.cgi?aredir=javascript:alert(document.cookie).
- Ths patches forces aredir to be a http:// or https:// link.
- Found by Nick Cleaton
- Add RFC822 compliant Date header to outgoing messages
- Handle the case where there is no Date header, so that the full version of the epoch is not used
- Documentation updates, to reflect changes over the last couple of years.
- Rewrote the installation of perl modules and c-client section
- Switch to the Date::Format and Date::Parse, which apparently come included on modern Linux distributions. Patch from Wayne Davison
- Switch from MD5 to Digest::MD5. Patch from Wayne Davison

check_logfiles is a plugin for Nagios which checks logfiles for defined patterns. check_logfiles project is capable of detecting logfile rotation.

If you tell it how the rotated archives look, it will also examine these files. Unlike check_logfiles, traditional logfile plugins were not aware of the gap which could occur, so under some circumstances they ignored what had happened between their checks.

A configuration file is used to specify where to search, what to search, and what to do if a matching line is found.

Installation:

1. `cd to the directory containing the packages source code and type `./configure to configure the package for your system. If youre using `csh on an old version of System V, you might need to type `sh ./configure instead to prevent `csh from trying to execute `configure itself.

Running `configure takes awhile. While running, it prints some messages telling which features it is checking for.

2. Type `make to compile the package.

3. Optionally, type `make check to run any self-tests that come with the package.

4. Type `make install to install the programs and any data files and documentation.

5. You can remove the program binaries and object files from the source code directory by typing `make clean. To also remove the files that `configure created (so you can compile the package for a different kind of computer), type `make distclean. There is also a `make maintainer-clean target, but that is intended mainly for the packages developers. If you use it, you may have to get all sorts of other programs in order to regenerate files that came with the distribution.

Rekall is a database front-end, somewhat in the style of MicroSoft Access. However, Rekall is not itself a database, and does not include a database.
By this we mean that data is stored somewhere else in an SQL server, and Rekall is fundementaly just a tool to extract, display and update that data (of course, it does lots more than that, it does forms and reports and scripting and .... you get the idea).
It is database agnostic, and does not have any preferred database in the sense that Access(tm) uses the Jet. database engine (although the Windows version can use the Jet database engine via an ODBC driver).
Rekall can do lots of the things that you would expect of a database front-end (or if it cant, let us know!). You can design and use forms and reports, you can construct database queries, and you can import and export data (actually, you can copy data, import is just copy file to table, and export is just copy table to file). You can also create reusable components which you can use in forms and reports, to reduce application development time.
Rekall can be scripted using the the Python language. You can arrange that a script is executed when various events occur (for instance, when the user changes the value of a control).
Scripts can be associated directly with the event, but you can also store scripts in script modules for more general use. And, of course, you have full access to all the modules that are available for Python. Plus, Rekall has an integrated Python debugger with syntax highlighting.
RekallRevealed is run as a community website to support the GPL version of Rekall. Rekall is being included by some of the Linux distributions, and commercial components and support are available from TotalRekall and from theKompany.
Enhancements:
Dynamic Layouts
- Dynamic layouts allow you to create forms where controls automatically resize depending on settings such as font sizes, and as the user resizes the form. This is based on QTs layout engine, althougn only a restricted set of functions are available.
Tool Boxes
- Personally, the author is not a fan of tool boxes, but they seem to be popular, so Rekall now supports them. If you still prefer the old context menu mechanism, you can turn tool boxes off.
Wizards
- Lots of the controls now have control wizards which prompt you for the important settings. Hopefully wizards will be avaialble for all controls by the time 2.3.x becomes 2.4.0
Stock Databases
- Stock databases. Rekall will come with some stock databases (actually there is only one at present, the demo database, but more will be added over time) which can be used to create your own database. In addition, you can download stock databases from the web. See the Rekall section on downloading the database that runs this website!
Manual
- The manual can now be accessed via a dedicated manual viewer (loosely modelled on QTs assistant program).
Other stuff
- Lots of bug fixes, lots of other smaller additions.
Enhancements:
- 2.2.6 is the now latest stable release.
- Mostly bug fixes since 2.2.4, particularly a problem related (I believe) to the default style used by Fedora Core 4

Guarddog is a firewall configuration utility for Linux systems. It is aimed at two groups of users. Novice to intermediate users who are not experts in TCP/IP networking and security, and those users who dont want the hastle of dealing with cryptic shell scripts and ipchains/iptables parameters.
Main features:
- Easy to use goal oriented GUI. You say what the firewall should do without having to explain all the details of how it should do it.
- Application protocol based. Unlike other tools, Guarddog does not require you to understand the ins and outs of IP packets and ports. Guarddog takes care of this for you. This also reduces the chances of configuration mistakes being made which are a prime source of security holes.
- Doesnt just generate the firewall once and forgets it. Guarddog lets you maintain and modify the firewall in place.
- Hosts/networks can be divided into Zones. Different zones can have different security policies for different.
- Supports the following network protocols: FTP, SSH, Telnet, Linuxconf, Corba, SMTP, DNS, Finger, HTTP, HTTPS, NFS, POP2, POP3, SUN RPC, Auth, NNTP, NETBIOS Name Service, NETBIOS Session Service, IMAP, Socks, Squid, pcANYWHEREstat, X Window System, Traceroute, ICQ, PowWow, IRC, PostgreSQL, MySQL, Ping, Quake, QuakeWorld, Quake 2, Who Is, Webmin, ICMP Source Quench, ICMP Redirect, Real Audio, Line Printer Spooler, syslog, NTP, NetMeeting, Gnutella, LDAP, LDAP-SSL, SWAT, Diablo II, Nessus, DHCP, AudioGalaxy, DirectPlay, Halflife, XDMCP and Telstras BigPond Cable, CDDB, MSN Messenger, VNC, PPTP, Kerberos, klogin, kshell, NIS, IMAPS, POP3S, ISAKMP, CVS, DICT, AIM, Fasttrack, Kazaa, iMesh, Grokster, Blubster, Direct Connect, WinMX, Yahoo! Messenger, AH, ESP, Jabber, EsounD, Privoxy, eDonkey2000, EverQuest, ICP, FreeDB, Elster, Yahoo games, Legato NetWorker backups, Novell Netware 5/6 NCP, Bittorrent, rsync, distcc, Jabber over SSL, PGP key server, Microsoft Media Server and gkrellm.
- Protocols not supported in the list above can be entered in directly.
- Supports router configurations.
- Runs on KDE 2 or 3, and Linux 2.2, 2.4 and 2.6 series kernels.
- Supports advanced Linux 2.4+ iptables features such as connection tracking and rate limited logging.
- Firewall scripts can be Imported/Exported for use on machines other than the current one.
- DHCP support.
- Uses a "what is not explicitly allowed, is denied" philosophy. Fail-safe design.
- Well documented with tutorials and reference material.
- Licensed under the terms of the GNU General Public License. Is Free and will remain Free.

rtldi is an ELF program interpreter that enables each main executable program to use its own runtime loader and shared libraries, independent of the default versions installed in /lib, and independent of any other main executable program.

Thus rtldi facilitates the simultaneous interoperation of programs that originally were linked using different generations of glibc6. In theory glibc6 is backward compatible (a given binary executable should run correctly using any subsequent version of glibc6), but in practice there have been enough bugs and glitches at various times to require workarounds.

Example: If the PT_INTERP of an executable a.elf is /2.2.4-24/rtldi (instead of /lib/ld-linux.so.2), then the executable runs effectively as if it were invoked via
/2.2.4-24/ld-linux.so.2 --library-path /2.2.4-24:$LD_LIBRARY_PATH /path/of/execve/a.elf args... and will use /2.2.4-24/libc.so.6 for its glibc6. rtldi uses its own path prefix in PT_INTERP as the prefix for ld-linux.so.2, and as the first directory path in the colon-separated list argument following --library-path.

The --library-path argument replaces LD_LIBRARY_PATH for a.elf only, without modifying LD_LIBRARY_PATH for a.elf or for any children that a.elf may invoke. (This is a feature of ld-linux.so.2.) Also, the process name remains "a.elf".

New ELF executables can specify the runtime loader by building with -Wl,--dynamic-linker=/path/to/rtldi. Old executables that specify /lib/ld-linux.so.2 for their PT_INTERP can be modified by using a binary file editor.

Find the Offset of the INTERP string by using readelf --program-headers a.elf. The replacement string cannot be longer, and must be terminated by