Commit 1bbd45a8 authored by Daniel Baumann's avatar Daniel Baumann

Adding upstream version 20080501+debian.

parents
Acknowledgements: libewf
Copyright (c) 2006-2008, Joachim Metz <forensics@hoffmannbv.nl>,
Hoffmann Investigations. All rights reserved.
This code is derived from information and software contributed by:
- Expert Witness Compression Format specification by Andrew Rosen
(http://www.arsdata.com/SMART/whitepaper.html)
- libevf from PyFlag by Michael Cohen
(http://pyflag.sourceforge.net/)
- Zlib for the implementation of the Zlib compression and optimized
Adler32 function
- Open SSL for the implementation of the MD5 hash algorithm
- libuuid for the implementation of GUID (UUID) calculation
- Wietse Venema for an example of the initial error handling code
Additional credits go to:
- Robert Jan Mora, Hoffmann Invesigations for testing and other contribution
(http://www.hoffmannbv.nl/)
- Rob Meijer, KLPD for providing libtool and header installation,
and ISO8601 date string support patches/adjustments.
- The OCFA team <ocfa@dnpa.nl>, for EWF Fuse integration.
- George M. Garner Jr. for his support with the native Windows port.
- Christophe Grenier for his various input and support for the SPEC file
autoconf/automake integration.
- Guy Voncken for his support and thorough testing of the EWF files
generated by libewf and for help with the deb package support.
- David Loveall <sourceforge@loveall.org> for creating mount-ewf,
a MacOS-X installation package and the providing for the delta segment file idea
- Several others for pointing out flaws within the product and its related
documentation. Refer to the project website for more information:
https://libewf.uitwisselplatform.nl
License: libewf
Copyright (c) 2006-2008, Joachim Metz <forensics@hoffmannbv.nl>,
Hoffmann Investigations. All rights reserved.
Refer to AUTHORS for acknowledgements.
Redistribution and use in source and binary forms, with or without modification,
are permitted provided that the following conditions are met:
- Redistributions of source code must retain the above copyright notice,
this list of conditions and the following disclaimer.
- Redistributions in binary form must reproduce the above copyright notice,
this list of conditions and the following disclaimer in the documentation
and/or other materials provided with the distribution.
- Neither the name of the creator, related organisations, nor the names of
its contributors may be used to endorse or promote products derived from
this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDER, COMPANY AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE
LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
This diff is collapsed.
Installation Instructions
*************************
Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005,
2006 Free Software Foundation, Inc.
This file is free documentation; the Free Software Foundation gives
unlimited permission to copy, distribute and modify it.
Basic Installation
==================
Briefly, the shell commands `./configure; make; make install' should
configure, build, and install this package. The following
more-detailed instructions are generic; see the `README' file for
instructions specific to this package.
The `configure' shell script attempts to guess correct values for
various system-dependent variables used during compilation. It uses
those values to create a `Makefile' in each directory of the package.
It may also create one or more `.h' files containing system-dependent
definitions. Finally, it creates a shell script `config.status' that
you can run in the future to recreate the current configuration, and a
file `config.log' containing compiler output (useful mainly for
debugging `configure').
It can also use an optional file (typically called `config.cache'
and enabled with `--cache-file=config.cache' or simply `-C') that saves
the results of its tests to speed up reconfiguring. Caching is
disabled by default to prevent problems with accidental use of stale
cache files.
If you need to do unusual things to compile the package, please try
to figure out how `configure' could check whether to do them, and mail
diffs or instructions to the address given in the `README' so they can
be considered for the next release. If you are using the cache, and at
some point `config.cache' contains results you don't want to keep, you
may remove or edit it.
The file `configure.ac' (or `configure.in') is used to create
`configure' by a program called `autoconf'. You need `configure.ac' if
you want to change it or regenerate `configure' using a newer version
of `autoconf'.
The simplest way to compile this package is:
1. `cd' to the directory containing the package's source code and type
`./configure' to configure the package for your system.
Running `configure' might take a while. 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 package's 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.
Compilers and Options
=====================
Some systems require unusual options for compilation or linking that the
`configure' script does not know about. Run `./configure --help' for
details on some of the pertinent environment variables.
You can give `configure' initial values for configuration parameters
by setting variables in the command line or in the environment. Here
is an example:
./configure CC=c99 CFLAGS=-g LIBS=-lposix
*Note Defining Variables::, for more details.
Compiling For Multiple Architectures
====================================
You can compile the package for more than one kind of computer at the
same time, by placing the object files for each architecture in their
own directory. To do this, you can use GNU `make'. `cd' to the
directory where you want the object files and executables to go and run
the `configure' script. `configure' automatically checks for the
source code in the directory that `configure' is in and in `..'.
With a non-GNU `make', it is safer to compile the package for one
architecture at a time in the source code directory. After you have
installed the package for one architecture, use `make distclean' before
reconfiguring for another architecture.
Installation Names
==================
By default, `make install' installs the package's commands under
`/usr/local/bin', include files under `/usr/local/include', etc. You
can specify an installation prefix other than `/usr/local' by giving
`configure' the option `--prefix=PREFIX'.
You can specify separate installation prefixes for
architecture-specific files and architecture-independent files. If you
pass the option `--exec-prefix=PREFIX' to `configure', the package uses
PREFIX as the prefix for installing programs and libraries.
Documentation and other data files still use the regular prefix.
In addition, if you use an unusual directory layout you can give
options like `--bindir=DIR' to specify different values for particular
kinds of files. Run `configure --help' for a list of the directories
you can set and what kinds of files go in them.
If the package supports it, you can cause programs to be installed
with an extra prefix or suffix on their names by giving `configure' the
option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
Optional Features
=================
Some packages pay attention to `--enable-FEATURE' options to
`configure', where FEATURE indicates an optional part of the package.
They may also pay attention to `--with-PACKAGE' options, where PACKAGE
is something like `gnu-as' or `x' (for the X Window System). The
`README' should mention any `--enable-' and `--with-' options that the
package recognizes.
For packages that use the X Window System, `configure' can usually
find the X include and library files automatically, but if it doesn't,
you can use the `configure' options `--x-includes=DIR' and
`--x-libraries=DIR' to specify their locations.
Specifying the System Type
==========================
There may be some features `configure' cannot figure out automatically,
but needs to determine by the type of machine the package will run on.
Usually, assuming the package is built to be run on the _same_
architectures, `configure' can figure that out, but if it prints a
message saying it cannot guess the machine type, give it the
`--build=TYPE' option. TYPE can either be a short name for the system
type, such as `sun4', or a canonical name which has the form:
CPU-COMPANY-SYSTEM
where SYSTEM can have one of these forms:
OS KERNEL-OS
See the file `config.sub' for the possible values of each field. If
`config.sub' isn't included in this package, then this package doesn't
need to know the machine type.
If you are _building_ compiler tools for cross-compiling, you should
use the option `--target=TYPE' to select the type of system they will
produce code for.
If you want to _use_ a cross compiler, that generates code for a
platform different from the build platform, you should specify the
"host" platform (i.e., that on which the generated programs will
eventually be run) with `--host=TYPE'.
Sharing Defaults
================
If you want to set default values for `configure' scripts to share, you
can create a site shell script called `config.site' that gives default
values for variables like `CC', `cache_file', and `prefix'.
`configure' looks for `PREFIX/share/config.site' if it exists, then
`PREFIX/etc/config.site' if it exists. Or, you can set the
`CONFIG_SITE' environment variable to the location of the site script.
A warning: not all `configure' scripts look for a site script.
Defining Variables
==================
Variables not defined in a site shell script can be set in the
environment passed to `configure'. However, some packages may run
configure again during the build, and the customized values of these
variables may be lost. In order to avoid this problem, you should set
them in the `configure' command line, using `VAR=value'. For example:
./configure CC=/usr/local2/bin/gcc
causes the specified `gcc' to be used as the C compiler (unless it is
overridden in the site shell script).
Unfortunately, this technique does not work for `CONFIG_SHELL' due to
an Autoconf bug. Until the bug is fixed you can use this workaround:
CONFIG_SHELL=/bin/bash /bin/bash ./configure CONFIG_SHELL=/bin/bash
`configure' Invocation
======================
`configure' recognizes the following options to control how it operates.
`--help'
`-h'
Print a summary of the options to `configure', and exit.
`--version'
`-V'
Print the version of Autoconf used to generate the `configure'
script, and exit.
`--cache-file=FILE'
Enable the cache: use and save the results of the tests in FILE,
traditionally `config.cache'. FILE defaults to `/dev/null' to
disable caching.
`--config-cache'
`-C'
Alias for `--cache-file=config.cache'.
`--quiet'
`--silent'
`-q'
Do not print messages saying which checks are being made. To
suppress all normal output, redirect it to `/dev/null' (any error
messages will still be shown).
`--srcdir=DIR'
Look for the package's source code in directory DIR. Usually
`configure' can determine that directory automatically.
`configure' also accepts some other, not widely useful, options. Run
`configure --help' for more details.
SUBDIRS = \
common \
libewf \
ewftools \
manuals
CONFIG_FILES = \
common/config.h \
common/config_windows.h
DEBIAN_FILES = \
debian/changelog \
debian/changelog.in \
debian/compat \
debian/control \
debian/copyright \
debian/cron.d.ex \
debian/emacsen-install.ex \
debian/emacsen-startup.ex \
debian/emacsen-remove.ex \
debian/init.d.ex \
debian/libewf.install \
debian/libewf.dirs \
debian/libewf.docs \
debian/libewf.postinst.debhelper \
debian/libewf.postrm.debhelper \
debian/libewf-default.ex \
debian/libewf-dev.dirs \
debian/libewf-dev.docs \
debian/libewf-dev.install \
debian/libewf-tools.dirs \
debian/libewf-tools.docs \
debian/libewf-tools.install \
debian/libewf.doc-base.EX \
debian/manpage.1.ex \
debian/manpage.sgml.ex \
debian/manpage.xml.ex \
debian/menu.ex \
debian/rules \
debian/postinst.ex \
debian/postrm.ex \
debian/preinst.ex \
debian/prerm.ex \
debian/shlibs.local.ex \
debian/shlibs.local.ex.in \
debian/watch.ex
DOCUMENT_FILES = \
doc/header.txt \
doc/header2.txt \
doc/tests.txt
INCLUDE_FILES = \
include/libewf.h.in \
include/libewf/definitions.h.in \
include/libewf/types.h.in
MANUAL_FILES = \
manuals/ewfacquire.1 \
manuals/ewfacquirestream.1 \
manuals/ewfexport.1 \
manuals/ewfinfo.1 \
manuals/ewfverify.1 \
manuals/libewf.3
MSVCPP_FILES = \
msvscpp/ewfacquire \
msvscpp/ewfacquire/ewfacquire.vcproj \
msvscpp/ewfacquirestream \
msvscpp/ewfacquirestream/ewfacquirestream.vcproj \
msvscpp/ewfalter \
msvscpp/ewfalter/ewfalter.vcproj \
msvscpp/ewfexport \
msvscpp/ewfexport/ewfexport.vcproj \
msvscpp/ewfinfo \
msvscpp/ewfinfo/ewfinfo.vcproj \
msvscpp/ewfverify \
msvscpp/ewfverify/ewfverify.vcproj \
msvscpp/libewf_dll \
msvscpp/libewf_dll/libewf_dll.vcproj \
msvscpp/libewf.sln
MACOSX_FILES = \
macosx/Introduction.rtf \
macosx/Introduction.rtf.in \
macosx/libewf.pmproj \
macosx/License.rtf \
macosx/Readme.rtf
REDHAT_FILES = \
libewf.spec \
libewf.spec.in
EXTRA_DIST = \
$(CONFIG_FILES) \
$(DEBIAN_FILES) \
$(DOCUMENT_FILES) \
$(INCLUDE_FILES) \
$(MANUAL_FILES) \
$(MSVCPP_FILES) \
$(MACOSX_FILES) \
$(REDHAT_FILES) \
libewf.pc \
libewf.pc.in
pkgconfigdir = $(libdir)/pkgconfig
pkgconfig_DATA = \
libewf.pc
include_HEADERS = \
include/libewf.h
pkginclude_HEADERS = \
include/libewf/definitions.h \
include/libewf/extern.h \
include/libewf/handle.h \
include/libewf/types.h
libtool: @LIBTOOL_DEPS@
cd $(srcdir) && $(SHELL) ./config.status --recheck
lib: library
library:
cd $(srcdir)/common && $(MAKE) $(AM_MAKEFLAGS)
cd $(srcdir)/libewf && $(MAKE) $(AM_MAKEFLAGS)
distclean: clean
/bin/rm -f Makefile
/bin/rm -f config.status config.cache config.log
/bin/rm -f common/config.h
/bin/rm -f include/libewf.h
/bin/rm -f include/libewf/definitions.h
/bin/rm -f include/libewf/types.h
/bin/rm -f libewf.pc
/bin/rm -f libewf.spec
/bin/rm -f debian/changelog
/bin/rm -f debian/shlibs.local.ex
/bin/rm -f macosx/Introduction.rtf
@for dir in ${subdirs}; do \
(cd $$dir && $(MAKE) distclean) \
|| case "$(MFLAGS)" in *k*) fail=yes;; *) exit 1;; esac; \
done && test -z "$$fail"
This diff is collapsed.
Library:
* improved internal code structure
* added raw read and write functions that will allow to read
'raw' chunk data
* improved read and write support uses delta segment files
no changes are stored in the EWF files use ewfexport to
create a set of changed EWF files for EnCase and FTK
* MD5 calculation no longer part of library
* added expirimental read/write support for > 2Gb segment files for EnCase 6.7
EWF tools:
* ewfexport no longer writes to stdout per default, default is now export.raw
specify '-t -' to write to stdout only for continuous raw output
Platform support:
* Microsoft Visual Studio 2005 (express) project files have been
added to the package
* Debian package support added
Dependencies
Libewf requires:
* zlib
* lybcrypto (OpenSSL)
or Windows Crypto API from the Windows Platform SDK
Creating a libewf DLL
Currently 2 methods of creating a libewf DLL are supported:
* using libtool
* using Microsoft Visual Studio C++
Creating a libewf DLL using libtool
You'll need Cygwin of MingW with a libtool version that supports
building DLLs.
By building the library:
./configure
make libewf
You should end up with a DLL something like:
libewf-<version>/libewf/.libs/cygewf-0.dll
Creating a libewf DLL using Microsoft Visual Studio C++
You'll need:
* Microsoft Visual Studio C++
The provided Visual Studio project files were created using
the 2005 express version. The express verion is available on the
Microsoft website
* Microsoft Platform API for the Windows Crypto API
The platform API verion is available on the Microsoft website
* The zlib DLL package including the .lib file available from the zlib
project site: http://www.gzip.org/zlib/
Extract the contents of the zlib DLL package to:
libewf-<version>/msvscpp/zlib
You should be able to build the libewf DLL using the provided
project files. Note that the project files contain a debug and release
configuration.
Using libewf DLL
Make sure you use define LIBEWF_DLL_IMPORT before including <libewf.h>,
i.e. CFLAGS=-DLIBEWF_DLL_IMPORT
When the libewf DLL was build with Microsoft Visual Studio
you'll need the zlib DLL. To run the executables on other platforms
than the build platform, you'll need the Microsoft Visual Studio redistributable DLLs.
Mac OS X
* missing libtoolize
* building multiple architure binaries
Missing libtoolize
Use glibtoolize instead
Building multiple architecture binaries
I.e. on Mac OS X 10.4 run the following commands:
CFLAGS="-isysroot /Developer/SDKs/MacOSX10.4u.sdk -arch ppc -arch i386" LDFLAGS="-Wl,-syslibroot,/Developer/SDKs/MacOSX10.4u.sdk -arch ppc -arch i386" ./configure --disable-dependency-tracking --prefix=$PWD/macosx/tmp/
make
make install
The binaries are installed in $PWD/macosx/tmp/
This diff is collapsed.
AM_CPPFLAGS = -I$(top_srcdir)/include
noinst_LTLIBRARIES = libcommon.la
libcommon_la_SOURCES = \
character_string.c character_string.h \
common.h \
date_time.c date_time.h \
endian.h \
error_string.c error_string.h \
file_io.c file_io.h \
memory.h \
notify.c notify.h \
string_conversion.c string_conversion.h \
system_string.c system_string.h \
types.h
distclean: clean
/bin/rm -f Makefile
This diff is collapsed.
/*
* Character string functions
*
* Copyright (c) 2006-2008, Joachim Metz <forensics@hoffmannbv.nl>,
* Hoffmann Investigations. All rights reserved.
*
* Refer to AUTHORS for acknowledgements.
*
* Redistribution and use in source and binary forms, with or without modification,
* are permitted provided that the following conditions are met:
*
* - Redistributions of source code must retain the above copyright notice,
* this list of conditions and the following disclaimer.
* - Redistributions in binary form must reproduce the above copyright notice,
* this list of conditions and the following disclaimer in the documentation
* and/or other materials provided with the distribution.
* - Neither the name of the creator, related organisations, nor the names of
* its contributors may be used to endorse or promote products derived from
* this software without specific prior written permission.
*
* THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDER, COMPANY AND CONTRIBUTORS
* "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
* THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
* ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE
* LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
* CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
* SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
* INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
* CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
* ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
* POSSIBILITY OF SUCH DAMAGE.
*/
#include "common.h"
#include "character_string.h"
#include "memory.h"
#include "notify.h"
#include "types.h"
/* Duplicates a string
* Returns the pointer to the duplicate string, or NULL on error
*/
character_t *libewf_string_duplicate(
character_t *string,
size_t size )
{
character_t *duplicate = NULL;
static char *function = "libewf_string_duplicate";
if( string == NULL )
{
return( NULL );
}
if( size == 0 )
{
return( NULL );
}
if( size > (size_t) SSIZE_MAX )
{
notify_warning_printf( "%s: invalid size value exceeds maximum.\n",
function );
return( NULL );
}
/* Add an additional character for the end of string
*/
size += 1;
duplicate = (character_t *) memory_allocate(
sizeof( character_t ) * size );
if( duplicate == NULL )
{
notify_warning_printf( "%s: unable to create duplicate string.\n",
function );
return( NULL );
}
if( string_copy(
duplicate,
string,
size ) == NULL )
{
notify_warning_printf( "%s: unable to set duplicate string.\n",
function );
memory_free(
duplicate );
return( NULL );
}
duplicate[ size - 1 ] = (character_t) '\0';
return( duplicate );
}
/* Returns the value represented by a string, returns 0 error
*/
int64_t libewf_string_to_int64(
const character_t *string,
size_t size )
{
character_t *end_of_string = NULL;
static char *function = "libewf_string_to_int64";
int64_t value = 0;
if( string == NULL )
{
notify_warning_printf( "%s: invalid string.\n",
function );
return( 0 );
}
if( size == 0 )
{
notify_warning_printf( "%s: string is emtpy.\n",
function );
return( 0 );
}
if( size > (size_t) SSIZE_MAX )
{
notify_warning_printf( "%s: invalid size value exceeds maximum.\n",
function );
return( 0 );
}