Free binary view software for linux

glTron project is a tron-like game with a 3D view.

glTron is a tron-like lightcycle game with a nice 3D perspective. 3D acceleration is recommended.

The Java Binary Enhancement Tool (JBET) is a general Java program analysis and manipulation tool. Existing class files can be disassembled, reassembled, or edited programmatically through the JBET API. JBET can also be used to create new Java class files from scratch. JBET uses a convenient internal representation of all the contents of Java binary (.class) files, allowing the user to edit the classes easily, in a structured manner.

JBET was developed as part of the DARPA Self-Protecting Mobile Agents project under the OASIS and Active Networks programs (contract number N66001-00-C-8602) in order to study automated software obfuscation.

The Java language was chosen for this project because of the (relative) ease of constructing binary editing tools provided by the large amount of type information present in the class files. Our two reports, the Obfuscation Techniques Evaluation Report, and the Obfuscation Report, are available from the download area. The obfuscation tool developed is not part of this release.

JBET was also used in the DARPA/AFRL Survivable Server project (contract number F30602-00-C-0183) to add additional security checks to the Java Standard Library. (The Java SecurityManager API does not support many desirable security checks, such as continued authorization of file accesses after opening.)

JBET was used to replace the native method references in the Java standard library with stubs that call a pluggable security policy. This tool, called Jpolicy, is also available for download at this website. Jpolicy is very incomplete at this time, but may be interesting to those working in Java security or changing the standard library themselves.

The internal representation of Java class files used by JBET is intented to make it easy for programmers to write Java binary code transforms. Each element of Java class files has a corresponding internal data structure: ClassInfo for entire classes, MethodInfo for methods, FieldInfo for fields, Snippit for code blocks, and Instruction for individual instructions. Snippit and Instruction understand Java opcode syntax and semantics, allowing automated creation of valid Java programs. A Java-compatible class verifier is also included.

Some code transforms are difficult to program directly by manipulating Java instructions. For those transforms, a directed acyclic graph (DAG) representation of code is available. In the DAG representation, each basic block has a corresponding DAG, with a set of input and output nodes. Edges in the graph connect "producer" nodes (such as constants, or the result of calculations) to "user" nodes (such as method calls or other calculations). Methods are divided into basic blocks and control flow is stored at the basic block level (possible because Java has only fixed jump targets)

JBET requires a Java 1.4 virtual machine to run, although it can operate on class files from earlier Java versions. The packaging and build environment supplied supports Linux and Windows with Cygwin; however, the build process is simple and could be performed manually on other platforms. Perl is required for regression testing.

Jpolicy requires a Java 1.4 virtual machine to build, either Linux or Windows NT/XP with Cygwin. gcc is required for building on Windows (supplied with Cygwin). The runtime system can be either Java 1.3 or 1.4 (with Suns JVM only), running on Linux or Windows NT/XP. Windows 9x and Windows 2000 may work as well, but have not been tested.

Installation

1. Install jdk 1.4.1.
2. Set CLASSPATH to jdk1.4.1/jre/lib/rt.jar
3. cd src; make
4. If that didnt work, examine the makefile. java or javac may not be in the path.
5. To build a jar file that can be used with "java -jar jbet.jar", run "make jar".
6. If you have perl installed, run the tests with "make test".
Optionally, run "make regen; make test".

Make a symbolic link from jbet3/bin/jbet to somewhere in your path.

Usage

JBET uses the JNI format for class names, and JNI type and method descriptors. For a summary of this syntax, use jbet help syntax. Suns JVM specification may also be helpful.

To look at a class disassembly, use jbet print. Try disassembling a class you have source for, and was built with debug info (-g): jbet -P < classpath > print < classname >. Suns JVM specification has an instruction reference.

Pdbv output a HTML view of a RPM or dpkg database. Its modular design allows easy addition of others package management database and export format (as xml).
The 1.x.x series are in Bash, the 2.x.x series are in Perl. Obviously, the output generation with 1.x.x is a lot slower than with the 2.x.x. While with the 1.x.x it should run on a daily basis, with the 2.x.x it should run on a hourly basis.
Main features:
- it does not require lucid/gtk+/qt or other big libs.
- it does not require a web server - but it can be used with a web server, as any
- other html files.
- it does not require a X server running, you can use a text mode browser that support
- frames as links.
- it does not require special privileges to access to the output. But access can
- be restricted by using chmod/chown (filesystem) or .htaccess (apache).
- since output is generated by a cronjob, access to the output is as fast as your
- computer is able to read/serve text files.

toast is a simple, self-contained tool for downloading, building, installing, uninstalling and managing software packages.
Unlike traditional package-management systems, toast is primarily intended to work directly with software distributed as source code, rather than in some precompiled or specialized binary format, such as RPM. Binary packages are also supported.
Enhancements:
- improve --interactive

Danpei is a Gtk+ based Image Viewer, works on X-Window system.
Danpei allows you to browse through your image files in thumbnail form, and it can rename, cut, and paste them easily with an interface similar to that of Windows Explorer.
It is distributed under the GNU General Public License.
Main features:
Rename files very easily
- You can rename your image files very easily only by changing their file names in entries, looking through them in Thumbnail format.
- This is very convenient when arranging the pictures taken in from your digital camera.
Cache files
- Created thumbnails are cached, and from next time, Danpei will display them quickly.
File operations like Windows Explorer
- You can move or copy your image files with cut & paste, and can create new directories or remove diretories.
- Cut & paste is possible to two or more files.
Drag and Drop
- You can move your image files from a directory to another one with drag and drop.
View/Edit image files
- You can view or edit your image files with your favorite applications. -- ImageMagick, Gimp etc.
Print out images.
- You can start an arbitrary command to print out your image files.
Small size
- The size of tarball is about 410KB, of elf binary after strip is about 180KB.

Superversion is a multi-user distributed version control system based on change sets. It aims to be an industrial-strength, open source alternative to commercial solutions that is equally easy to use (or even easier) and similarly powerful. In fact, intuitive and efficient usability has been one of the top priorities in Superversions development from the very beginning.
If youre frustrated with CVS - as so many developers before you - and dont want to spend money on a version management software, try Superversion today! Superversion is ublished under the GPL and free to use even in commercial environments.
Main features:
- Very easy download, installation and setup in just a few clicks
- Platform-independent; supported on Windows, Linux, OS/2, OpenVMS (should run on Macs too - feedback welcome!)
- Graphical user interface for all operations
- Fully transactional internal database - very strong protection against data loss
- Can be used with any editor or file-based IDE
- Compressed diff view for every file accessible in just one click
- Instant overview of all new/changed/deleted files in work area
- Changes can be collected in a buffer before being committed to repository
- Branching
- Branch merging
- All file changes stored as diffs (low space consumption even for binary files)
- Report functions: fulltext search, state comparison, file history
- Support for multiple work areas per project (simultaneous work on different versions)
- Graphical project history view
- Keyword replacement (analogous to CVS)
- Convenient selection of files and directories to be ignored
- Marker system to assign human-readable labels to versions
- Comments assignable to every version, every file
- Export of any recorded version as zip file, complete directory or file-wise
- File type (binary/text) detected automatically (manual override possible)
- Help text in most dialogs
Enhancements:
- The user interface is faster and more responsive in many places.
- There is a new dialog for adding work areas.