Free 3.9 software for linux

ProGuard is a free Java class file shrinker, optimizer, and obfuscator. ProGuard project can detect and remove unused classes, fields, methods, and attributes. It can then optimize bytecode and remove unused instructions.
Finally, it can rename the remaining classes, fields, and methods using short meaningless names. The resulting jars are smaller and harder to reverse-engineer.
More compact jar files also means smaller storage requirements, faster transfer of applications across networks, faster loading, and smaller memory footprints.
ProGuards main advantage compared to other Java obfuscators is probably its compact template-based configuration. A few intuitive command line options or a simple configuration file are usually sufficient. For instance, the following configuration option preserves all applets in a jar:
-keep public class * extends java.applet.Applet
The user manual explains all available options and shows more examples of this powerful configuration style.
ProGuard is fast. It only takes seconds to process programs and libraries of several megabytes. The results section presents actual figures for a number of applications.
ProGuard is a command-line tool with an optional graphical user interface. It also comes with plugins for Ant and for the J2ME Wireless Toolkit.
ProGuard is a Java class file shrinker, optimizer, and obfuscator. The shrinking step detects and removes unused classes, fields, methods, and attributes. The optimization step analyzes and optimizes the bytecode of the methods. The obfuscation step renames the remaining classes, fields, and methods using short meaningless names. The resulting jars are smaller and harder to reverse-engineer.
ProGuard can also be used to list unused fields and methods in an application, and to print out the internal structure of class files.
ProGuard typically reads the input jars (or wars, ears, zips, or directories). It then shrinks, optimizes, and obfuscates them. It then writes the results to one or more output jars (or wars, ears, zips, or directories). The input jars can optionally contain resource files. ProGuard copies all non-class resource files from the input jars to the output jars. Their names and contents remain unchanged.
ProGuard requires the library jars (or wars, ears, zips, or directories) of the input jars to be specified. It can then reconstruct class hierarchies and other class dependencies, which are necessary for proper shrinking, optimization, and obfuscation. The library jars themselves always remain unchanged. You should still put them in the class path of your final application.
In order to determine which code has to be preserved and which code can be discarded or obfuscated, you have to specify one or more entry points to your code. These entry points are typically classes with main methods, applets, midlets, etc.
- In the shrinking step, ProGuard starts from these seeds and recursively determines which classes and class members are used. All other classes and class members are discarded.
- In the optimization step, ProGuard further optimizes the code. Among other optimizations, classes and methods that are not entry points can be made final, and some methods may be inlined.
- In the obfuscation step, ProGuard renames classes and class members that are not entry points. In this entire process, keeping the entry points ensures that they can still be accessed by their original names.
Any classes or class members of your code that are created or invoked dynamically (that is, by name) have to be specified as entry points too. It is generally impossible to determine these cases automatically, but ProGuard will offer some suggestions if keeping some classes or class members appears necessary. For proper results, you should at least be somewhat familiar with the code that you are processing.
ProGuard does handle Class.forName("SomeClass") and SomeClass.class constructs automatically. The referenced classes are preserved in the shrinking phase, and the string arguments are properly replaced in the obfuscation phase. With variable string arguments, it is generally impossible to determine their possible values (they might be read from a configuration file, for instance).
However, as mentioned, ProGuard will note constructs like "(SomeClass)Class.forName(variable).newInstance()". These might be an indication that the class or interface SomeClass and/or its implementations may need to be preserved. You can then adapt your configuration accordingly.
Whats New in 3.9 Stable Release:
- This release fixes a number of bugs.
- Notably, ".class" constructs compiled in Java 6 are now handled correctly.
- The optimization step now avoids a possible division by 0 and correctly processes local variables with indices larger than 255.
- The documentation and examples have been updated.
Whats New in 4.0 Beta Development Release:
- Added preverifier for Java 6 and Java Micro Edition, with new option -dontpreverify.
- Added new option -target to modify java version of processed class files.
- Made -keep options more orthogonal and flexible, with option modifiers allowshrinking, allowoptimization, and allowobfuscation.
- Added support for configuration by means of annotations.
- Improved shrinking of unused annotations.
- Added check on modification times of input and output, to avoid unnecessary processing, with new option -forceprocessing.
- Added new options -flattenpackagehierarchy and -repackageclasses (replacing -defaultpackage) to control obfuscation of packages names.
- Added new options -adaptresourcefilenames and -adaptresourcefilecontents, with file filters, to update resource files corresponding to obfuscated class names.
- Now respecting naming rule for nested class names (EnclosingClass$InnerClass) in obfuscation step, if InnerClasses attributes or EnclosingMethod attributes are being kept.
- Added new inter-procedural optimizations: method inlining and propagation of constant fields, constant arguments, and constant return values.
- Added optimized local variable allocation.
- Added over 250 new peephole optimizations.
- Improved making classes and class members public or protected.
- Now printing notes on suspiciously unkept classes in parameters of specified methods.
- Now printing notes for class names that dont seem to be fully qualified.
- Added support for uppercase filename extensions.
- Rewritten class file I/O code.
- Updated documentation and examples.

eZ publish is a popular open source content management system and development framework. eZ publish project is distributed, developed and supported by eZ systems. eZ systems is a commercial company, founded by experienced and open-minded people. The company builds its business by providing services around the eZ publish system. For more information about eZ systems, read the "What is eZ systems?" section.
eZ publish allows the development of highly professional and customized internet solutions and dynamic web applications. It can be used to build anything from a personal homepage to a multinational corporate website with role based multiuser access, online shopping, discussion forums and other advanced functionality. In addition, because of its nature of openness, eZ publish can be easily plugged into, communicate and coexist with existing IT-solutions.
eZ publish comes with a wide range of advanced built-in features, which make it possible to develop professional, complex, secure and reliable solutions within a short amount of time. In addition to the built-in features, the system allows for extensions and custom modifications in almost any direction. Unlike other content management systems, eZ publish delivers a flexible, generic solution with very few limitations. In other words, this is a scalable and dynamic system that companies and organizations can grow with.
eZ publish is platform independent. It can be used on Windows and several UNIX variants such as OS X, Linux, FreeBSD, Solaris, IRIX, etc. In addition, eZ publish is also database independent; if a specific database isnt supported, it is possible to write a driver without modifying any kernel code.
eZ publish is open software, supporting open standards. The software is constructed following strict development processes in order to ensure high technical quality and usability.
eZ publish is dual licensed. There is a GPL (General Public License) and a professional license. Using the GPL license, people can build their own open source applications and thereby contribute to the development of free and open software. The professional license allows companies to make and sell commercial software that is developed using and/or built upon the eZ publish system.
Enhancements:
- Several bugfixes and enhancements.
- The command line package tool ezpm.php has been updated: list, import, and install commands have been changed to match the admin interface functionality.
- The ezinstallscript and ezextension items are supported by the add command. ezpm is allowed to set the vendor.
- Enhancement #010347 (progress output for correctxmltext.php and updatetypedrelation.php) has been implemented.

tcpdump is a handy little library which provides a packet filtering mechanism based on the BSD packet filter (BPF).

Most notably, tcpdump needs this to work, and there is also a perl module (still in beta) which can use this as well. In plain english, if you want to write your own network traffic analyzer, this is the place to start.

prerex project is an interactive (command-line) editor and a LaTeX macro support package that can be used to create very attractive and readable prerequisite charts.
A prerequisite chart is a network of course boxes linked by prerequisite and co-requisite arrows.
Enhancements:
- The patch for kpdf has been modified so that correct chart coordinates are returned when the document display is smaller than the kpdf window.

Mtools is a collection of utilities to access MS-DOS disks from Unix without mounting them. The project supports Win95 style long file names, OS/2 Xdf disks and 2m disks (store up to 1992k on a high density 3 1/2 disk).
Mtools can now handle the long filenames of Windows NT and Windows 95. Mtools is maintained by David Niemi and me (Alain Knaff). Mtools-3.9.9 has been released on March 3rd, 2003.
Enhancements:
- This is mostly a maintainance release which fixes a couple of bugs, addresses warnings raised by gcc4, and merges some platform-specific patches (MingW, NetBSD, Redhat/Fedora, Cygwin, Solaris).

Valknut project is a peer-2-peer file-sharing program (similar to Kazaa, Soulseek or eDonkey) that uses the Direct Connect protocol.
It is compatible with other DC clients, such as the original DC from Neomodus, and DC++.
Main features:
- open source
- multiplatform (Linux,Win32,OSX ...)
- multilanguage
- multihub connections
- multihub search
- multi-/chunkdownload (download one file from multiple sources at the same time)
- firewall support
- sounds
- favorite hub list
- online translator
- load/save search results
- autosearch new sources
- socks support for linux (http://www.inet.no/dante/)
- proxy support for hublists
- support bz2 share lists
- support xml share lists
- support ssl transfers
- support ssl hub connections (e.g. hub use sslproxy)
- support secure chat (not secure against "Man In The Middle Attack")
- chat emoticons
- tiger tree hash (TTH) support

CableTV is a CableCrypt decoder for Linux. It has been tested with BT878 cards under kernel 2.2.x and 2.4.x, and provides full decryption of Wiener Telekabel Telekino (Austria), but reported to work with many stations over europe. It works yet only with PAL. Chroma and polarity inversion is supported. It has support for color MMX decoding and b/w x86 assembler decoding.
Enhancements:
- fixed compile errors with gcc-2.95.x
- reduced audio on 10 sec. delay to 1 sec.
- support for long options
- use pci utils for bt848 address (Manuel Estrada Sainz)
- drop root privilege ASAP (Manuel Estrada Sainz)
- STRANGE_SYNC_PROBLEMS patch (Manuel Estrada Sainz)
- debianized with help from Manuel Estrada Sainz
- inline MMX and asm locking stuff, we dont need nasm anymore, yes!
- enabled old C decode routine, maybe we get it to run on another platform than i386
- made code ANSI C conform, compiles now with -ansi
- added initial autoconf support
- changed default decode routine to -r4
- major code cleanup in cablecrypt-*.c files
- add PAL interpolation to C mode (option -r2)