Difference between pages "Linux Logical Volume Manager (LVM)" and "Plaso"

From ForensicsWiki
(Difference between pages)
Jump to: navigation, search
(Mounting an LVM from a device)
 
(File Formats)
 
Line 1: Line 1:
{{expand}}
+
{{Infobox_Software |
 +
  name = plaso |
 +
  maintainer = [[Kristinn Gudjonsson]], [[Joachim Metz]] |
 +
  os = [[Linux]], [[Mac OS X]], [[Windows]] |
 +
  genre = {{Analysis}} |
 +
  license = {{APL}} |
 +
  website = [https://code.google.com/p/plaso/ code.google.com/p/plaso/] |
 +
}}
  
The [[Linux]] Logical Volume Manager, is commonly abbreviated to LVM. Although LVM can used for other [http://en.wikipedia.org/wiki/Logical_Volume_Management Logical Volume Management] variants as well.
+
Plaso (plaso langar að safna öllu) is the Python based back-end engine used by tools such as log2timeline for automatic creation of a super timelines. The goal of log2timeline (and thus plaso) is to provide a single tool that can parse various log files and forensic artifacts from computers and related systems, such as network equipment to produce a single correlated timeline. This timeline can then be easily analysed by forensic investigators/analysts, speeding up investigations by correlating the vast amount of information found on an average computer system. Plaso is intended to be applied for creating super timelines but also supports creating [http://blog.kiddaland.net/2013/02/targeted-timelines-part-i.html targeted timelines].
  
Not all forensic tools have support for Linux Logical Volume Manager (LVM) volumes, but most modern Linux distributions do.
+
The Plaso project site also provides [[4n6time]], formerly "l2t_Review", which is a cross-platform forensic tool for timeline creation and review by [[David Nides]].
  
== Forensic analysis ==
+
== Supported Formats ==
The metadata area of a LVM Physical Volume can contain multiple versions of metadata section that contains the LVM Volume Group definitions, including a creation date and time value.
+
  
== Mounting an LVM ==
+
=== Storage Media Image File Formats ===
=== Mounting an LVM from an image ===
+
Storage Medis Image File Format support is provided by [[dfvfs]].
If you have an image mount the LVM read-only on a loopback device (e.g. /dev/loop1) by:
+
<pre>
+
sudo losetup -r -o $OFFSET /dev/loop1 image.raw
+
</pre>
+
  
Note that the offset is in bytes.
+
=== Volume System Formats ===
 +
Volume System Format support is provided by [[dfvfs]].
  
If you need to write to the image, e.g. for recovery, use [[xmount]] to write the changes to a [[shadow file]] (or cachefile in xmount terminology).
+
=== File System Formats ===
<pre>
+
File System Format support is provided by [[dfvfs]].
sudo xmount --in dd --cache sda.shadow sda.raw image/
+
</pre>
+
  
You can then safely mount the LVM in read-write mode (just omit the -r in the previous losetup command).
+
=== File Formats ===
 +
* [[Property list (plist)|Binary property list (plist) format]] using [[binplist]]
 +
* [[Extensible Storage Engine (ESE) Database File (EDB) format]]using [[libesedb]]
 +
* [[Internet Explorer History File Format]] (also known as MSIE 4 - 9 Cache Files or index.dat) using [[libmsiecf]]
 +
* [[OLE Compound File]] using [[libolecf]]
 +
* [[Windows Event Log (EVT)]] using [[libevt]]
 +
* [[Windows NT Registry File (REGF)]] using [[libregf]]
 +
* [[LNK|Windows Shortcut File (LNK) format]] using [[liblnk]]
 +
* [[Windows XML Event Log (EVTX)]] using [[libevtx]]
 +
* Syslog
  
To remove this mapping afterwards run:
+
<b>TODO expand this list</b>
<pre>
+
sudo losetup -d /dev/loop1
+
</pre>
+
  
To scan for new physical volumes:
+
== History ==
<pre>
+
Plaso is a Python-based rewrite of the Perl-based [[log2timeline]] initially created by [[Kristinn Gudjonsson]]. Plaso builds upon the [[SleuthKit]], [[libyal]] and other projects.
lvm pvscan
+
</pre>
+
  
You cannot unmount an active volume group. To detach (or deactivate) the volume group:
+
== See Also ==
<pre>
+
* [[dfvfs]]
vgchange -a n $VOLUMEGROUP
+
* [[log2timeline]]
</pre>
+
 
+
Where $VOLUMEGROUP is the corresponding name of the volume group
+
 
+
The individual volume devices are now available in:
+
<pre>
+
/dev/mapper/$VOLUMEGROUP-$VOLUMENAME
+
</pre>
+
 
+
=== Mounting an LVM from a device ===
+
 
+
To list the Volume Groups (VG) run:
+
<pre>
+
pvs
+
</pre>
+
 
+
To list information about a Volume Group (VG) run:
+
<pre>
+
lvdisplay $VOLUMEGROUP
+
</pre>
+
 
+
The field "LV Name" provides the volume name
+
 
+
To make the volume group known to the system (only if it was previously exported using ''vgexport'' command, note that ''vgimport'' would alter the data in the LVM2 header):
+
<pre>
+
vgimport $VOLUMEGROUP
+
</pre>
+
 
+
And activate the volumes in the volume group (sometimes you need to run ''vgscan'' first):
+
<pre>
+
vgchange -a y $VOLUMEGROUP
+
</pre>
+
 
+
The individual volume devices are now available in:
+
<pre>
+
/dev/mapper/$VOLUMEGROUP-$VOLUMENAME
+
</pre>
+
 
+
These now can be analyzed with e.g. a tool like the [[Sleuthkit]] or loop-back mounted.
+
 
+
To read-only loop-back mount an individual volume:
+
<pre>
+
mount -o ro,loop /dev/mapper/$VOLUMEGROUP-$VOLUMENAME filesystem/
+
</pre>
+
 
+
== Also see ==
+
* [[:Category:File Systems | File Systems]]
+
  
 
== External Links ==
 
== External Links ==
* [http://en.wikipedia.org/wiki/Logical_Volume_Manager_%28Linux%29 Wikipedia article on Logical Volume Manager]
+
* [https://code.google.com/p/plaso/ Project site]
* [http://www.tldp.org/HOWTO/LVM-HOWTO/ LVM Howto], by [http://www.tldp.org/ The Linux Documentation Project]
+
* [https://sites.google.com/a/kiddaland.net/plaso/home Project documentation]
* [http://www.sourceware.org/lvm2/ LVM2 Resource Page]
+
* [http://blog.kiddaland.net/ Project blog]
* [http://www.redhat.com/magazine/009jul05/features/lvm2/ The Linux Logical Volume Manager], by Heinz Mauelshagen and Matthew O'Keefe
+
* [https://sites.google.com/a/kiddaland.net/plaso/usage/4n6time 4n6time]
* [http://www.datadisk.co.uk/html_docs/redhat/rh_lvm.htm LVM cheatsheet], by [[RedHat]]
+
* [http://content.hccfl.edu/pollock/aunix1/lvm.htm Unix/Linux Administration Logical Volume Management Guide], by Wayne Pollock, 2005
+
* [http://lvb.sti.fce.vutbr.cz/public/LinuxAlt_2009/2009_11_08_LA_04_LVM/2009_11_08_LA_04_LVM.pdf LVM2 – data recovery], by Milan Brož, LinuxAlt 2009
+
 
+
[[Category:Volume Systems]]
+

Revision as of 03:21, 3 June 2014

plaso
Maintainer: Kristinn Gudjonsson, Joachim Metz
OS: Linux, Mac OS X, Windows
Genre: Analysis
License: APL
Website: code.google.com/p/plaso/

Plaso (plaso langar að safna öllu) is the Python based back-end engine used by tools such as log2timeline for automatic creation of a super timelines. The goal of log2timeline (and thus plaso) is to provide a single tool that can parse various log files and forensic artifacts from computers and related systems, such as network equipment to produce a single correlated timeline. This timeline can then be easily analysed by forensic investigators/analysts, speeding up investigations by correlating the vast amount of information found on an average computer system. Plaso is intended to be applied for creating super timelines but also supports creating targeted timelines.

The Plaso project site also provides 4n6time, formerly "l2t_Review", which is a cross-platform forensic tool for timeline creation and review by David Nides.

Supported Formats

Storage Media Image File Formats

Storage Medis Image File Format support is provided by dfvfs.

Volume System Formats

Volume System Format support is provided by dfvfs.

File System Formats

File System Format support is provided by dfvfs.

File Formats

TODO expand this list

History

Plaso is a Python-based rewrite of the Perl-based log2timeline initially created by Kristinn Gudjonsson. Plaso builds upon the SleuthKit, libyal and other projects.

See Also

External Links