Initial import.

Package-Manager: portage-2.0.51-r15

1 files changed, 24 insertions, 0 deletions

diff --git a/app-forensics/mac-robber/metadata.xml b/app-forensics/mac-robber/metadata.xml
new file mode 100644
index 000000000000..39c63700da50
--- /dev/null
+++ b/app-forensics/mac-robber/metadata.xml
@@ -0,0 +1,24 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
+<pkgmetadata>
+<herd>forensics</herd>
+<maintainer>
+  <email>forensics@gentoo.org</email>
+    <name>Forensics Herd</name>
+</maintainer>
+<longdescription>
+mac-robber is a digital forensics and incident response tool that collects data from allocated files in a mounted file system. 
+The data can be used by the mactime tool in The Sleuth Kit to make a timeline of file activity. The mac-robber tool is based on 
+the grave-robber tool from TCT and is written in C instead of Perl. 
+
+mac-robber requires that the file system be mounted by the operating system, unlike the tools in The Sleuth Kit that process the 
+file system themselves. Therefore, mac-robber will not collect data from deleted files or files that have been hidden by 
+rootkits. mac-robber will also modify the Access times on directories that are mounted with write permissions. 
+
+
+"What is mac-robber good for then", you ask? mac-robber is useful when dealing with a file system that is not supported by The 
+Sleuth Kit or other forensic tools. mac-robber is very basic C and should compile on any UNIX system. Therefore, you can run 
+mac-robber on an obscure, suspect UNIX file system that has been mounted read-only on a trusted system. I have also used 
+mac-robber during investigations of common UNIX systems such as AIX.
+</longdescription>
+</pkgmetadata>