linux-kernel - Parsing Structures postmortem from memory dump

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <4820ABA5.3020705@gmail.com>
Date:	Tue, 06 May 2008 15:04:05 -0400
From:	Adrian Sud <pigsflew2008@...il.com>
To:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Parsing Structures postmortem from memory dump

Hi,

I am working on a project attempting to extend the volatility toolkit 
(www.volatilesystems.com) to read Linux memory; for now I am attempting 
to support Kernel 2.6.22-14 using i686 arch.

What I mean to do is have it first identify that the image is from a 
linux environment, and then parse out the processes that were running 
when the image was taken.

I've looked at /include/linux/sched.h and tried to understand the 
task_struct structure, but it appears to be variable-length, determined 
at compile time, and I can't tell exactly how these are stored 
throughout memory--In a list? a tree?

If anyone can point me to more information toward finding out how to 
trace this, I would appreciate it.

Thank you,

Adrian Sud

UMass Amherst
Dept. of Computer Science
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/