2008-03-09 02:56:02 +01:00
|
|
|
# $NetBSD: Makefile,v 1.5 2008/03/09 01:56:02 dhowland Exp $
|
initial import of memdump
DESCR:
What can you expect to find in a system memory dump? Bits from the
operating system, from running processes, and from every file and
directory that has been accessed recently. Depending on the operating
system you may even find some information from deleted files and
exited processes, although that information tends to be short-lived.
To dump physical memory:
memdump | nc host port
memdump | openssl s_client -connect host:port
For best results send output off-host over the network. Writing to
file risks clobbering all the memory in the file system cache. Use
netcat, stunnel, or openssl, depending on your requirements.
With the exception of Linux, dumping UNIX system memory is a tricky
business because /dev/mem has holes that one has to carefully skip
around in order not to read nonsense or even miss information.
This software was tested on Linux, Solaris, FreeBSD, OpenBSD, and
is distributed under the IBM Public License.
2005-09-03 17:49:30 +02:00
|
|
|
#
|
|
|
|
|
|
|
|
|
|
DISTNAME= memdump-1.01
|
2005-11-02 18:59:54 +01:00
|
|
|
CATEGORIES= sysutils
|
initial import of memdump
DESCR:
What can you expect to find in a system memory dump? Bits from the
operating system, from running processes, and from every file and
directory that has been accessed recently. Depending on the operating
system you may even find some information from deleted files and
exited processes, although that information tends to be short-lived.
To dump physical memory:
memdump | nc host port
memdump | openssl s_client -connect host:port
For best results send output off-host over the network. Writing to
file risks clobbering all the memory in the file system cache. Use
netcat, stunnel, or openssl, depending on your requirements.
With the exception of Linux, dumping UNIX system memory is a tricky
business because /dev/mem has holes that one has to carefully skip
around in order not to read nonsense or even miss information.
This software was tested on Linux, Solaris, FreeBSD, OpenBSD, and
is distributed under the IBM Public License.
2005-09-03 17:49:30 +02:00
|
|
|
MASTER_SITES= http://www.porcupine.org/forensics/
|
|
|
|
|
|
|
|
|
|
MAINTAINER= pancake@phreaker.net
|
|
|
|
|
HOMEPAGE= http://www.porcupine.org/forensics/tct.html
|
2005-09-28 09:38:35 +02:00
|
|
|
COMMENT= Memory dumper for UNIX-like systems
|
initial import of memdump
DESCR:
What can you expect to find in a system memory dump? Bits from the
operating system, from running processes, and from every file and
directory that has been accessed recently. Depending on the operating
system you may even find some information from deleted files and
exited processes, although that information tends to be short-lived.
To dump physical memory:
memdump | nc host port
memdump | openssl s_client -connect host:port
For best results send output off-host over the network. Writing to
file risks clobbering all the memory in the file system cache. Use
netcat, stunnel, or openssl, depending on your requirements.
With the exception of Linux, dumping UNIX system memory is a tricky
business because /dev/mem has holes that one has to carefully skip
around in order not to read nonsense or even miss information.
This software was tested on Linux, Solaris, FreeBSD, OpenBSD, and
is distributed under the IBM Public License.
2005-09-03 17:49:30 +02:00
|
|
|
|
2005-09-28 09:38:35 +02:00
|
|
|
USE_TOOLS+= gmake
|
|
|
|
|
BUILD_TARGET= what
|
2008-03-09 02:56:02 +01:00
|
|
|
INSTALLATION_DIRS= sbin
|
initial import of memdump
DESCR:
What can you expect to find in a system memory dump? Bits from the
operating system, from running processes, and from every file and
directory that has been accessed recently. Depending on the operating
system you may even find some information from deleted files and
exited processes, although that information tends to be short-lived.
To dump physical memory:
memdump | nc host port
memdump | openssl s_client -connect host:port
For best results send output off-host over the network. Writing to
file risks clobbering all the memory in the file system cache. Use
netcat, stunnel, or openssl, depending on your requirements.
With the exception of Linux, dumping UNIX system memory is a tricky
business because /dev/mem has holes that one has to carefully skip
around in order not to read nonsense or even miss information.
This software was tested on Linux, Solaris, FreeBSD, OpenBSD, and
is distributed under the IBM Public License.
2005-09-03 17:49:30 +02:00
|
|
|
|
|
|
|
|
do-install:
|
|
|
|
|
${INSTALL_PROGRAM} ${WRKSRC}/memdump ${PREFIX}/sbin
|
2006-04-20 15:36:34 +02:00
|
|
|
${INSTALL_MAN} ${WRKSRC}/memdump.1 ${PREFIX}/${PKGMANDIR}/man1/
|
initial import of memdump
DESCR:
What can you expect to find in a system memory dump? Bits from the
operating system, from running processes, and from every file and
directory that has been accessed recently. Depending on the operating
system you may even find some information from deleted files and
exited processes, although that information tends to be short-lived.
To dump physical memory:
memdump | nc host port
memdump | openssl s_client -connect host:port
For best results send output off-host over the network. Writing to
file risks clobbering all the memory in the file system cache. Use
netcat, stunnel, or openssl, depending on your requirements.
With the exception of Linux, dumping UNIX system memory is a tricky
business because /dev/mem has holes that one has to carefully skip
around in order not to read nonsense or even miss information.
This software was tested on Linux, Solaris, FreeBSD, OpenBSD, and
is distributed under the IBM Public License.
2005-09-03 17:49:30 +02:00
|
|
|
|
|
|
|
|
.include "../../mk/bsd.pkg.mk"
|
