Login or Register to Ask a Question and Join Our Community


Software Releases - RSS News

Open Computer Forensics Architecture 2.1.0 (Default branch)

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News Open Computer Forensics Architecture 2.1.0 (Default branch)
# 1  
Old 03-18-2008
Open Computer Forensics Architecture 2.1.0 (Default branch)
The Open Computer Forensics Architecture (OCFA) isa modular computer forensics framework to automatethe digital forensic process, to speed up theinvestigation and give tactical investigatorsdirect access to the seized data through an easyto use search and browse interface. Thearchitecture forms an environment where existingforensic tools and libraries can be easily pluggedinto the architecture and can thus be made part ofthe recursive extraction of data and metadata fromdigital evidence. It aims to be highly modular,robust, fault tolerant, recursive, and scalable inorder to be usable in large investigations thatspawn numerous terabytes of evidence data andcover hundreds of evidence items.License: GNU General Public License (GPL)Changes:
This version includes some refactored subsystems that should make the architecture a bit faster and easier to integrate with other programming languages like Java and Perl. With the new treegraph library, it should now be a lot simpler to create custom treegraph-based modules for the architecture.Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question

LEARN ABOUT BSD

acc

ACC(4)							     Kernel Interfaces Manual							    ACC(4)

NAME

       acc - ACC LH/DH IMP interface

SYNOPSIS

       /sys/conf/SYSTEM:
	    NACC 0    # ACC LH/DH ARPAnet IMP interface
	    PLI  YES  # LH/DH is connected to a PLI

DESCRIPTION

       The  acc device provides a Local Host/Distant Host interface to an IMP.	It is normally used when participating in the DARPA Internet.  The
       controller itself is not accessible to users, but instead provides the hardware support to the IMP interface  described	in  imp(4).   When
       configuring, the imp(NIMP) pseudo-device must also be included.

DIAGNOSTICS

       acc%d: not alive.  The initialization routine was entered even though the device did not autoconfigure.	This indicates a system problem.

       acc%d:  can't  initialize.  Insufficient UNIBUS resources existed to initialize the device.  This is likely to occur when the device is run
       on a buffered data path on an 11/750 and other network interfaces are also configured to use buffered data paths, or when it is	configured
       to use buffered data paths on an 11/730 (which has none).

       acc%d:  imp doesn't respond, icsr=%b.  The driver attempted to initialize the device, but the IMP failed to respond after 500 tries.  Check
       the cabling.

       acc%d: stray xmit interrupt, csr=%b.  An interrupt occurred when no output had previously been started.

       acc%d: output error, ocsr=%b, icsr=%b.  The device indicated a problem sending data on output.

       acc%d: input error, csr=%b.  The device indicated a problem receiving data on input.

       acc%d: bad length=%d.  An input operation resulted in a data transfer of less than 0 or more than 1008 bytes of data into memory (according
       to the word count register).  This should never happen as the maximum size of a host-IMP message is 1008 bytes.

3rd Berkeley Distribution					   July 26, 1987							    ACC(4)