You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using plaso to process a full disk image taken from a OpenBSD virtual machine. As typical for OpenBSD, the disk is split into multiple partitions, each containing some part of the file system.
Plaso only processes data from a single partition. Other partitions are not processed and the respective data is missing in the resulting timeline.
Given the technical details (see additional context below), I think even this processing of the single partition is only due to lucky alignment of partition offsets.
The operating system you are running Plaso on (Not the operating system of the image/files you're trying to analyze):
Debian 12
Steps to reproduce the behavior including command line and arguments and output:
running log2timeline --storage_file test.plaso ~/Downloads/openbsd/image.raw --partitions all produces a storage file containing info from only the "root" partition of OpenBSD. Following timeline was created with psort -w timeline.csv test.plaso timeline.csv
To see that partitions are missing from the processing, notice the lack of data on files under /var
I am working with a sample disk image of 20GB size. If needed, I can see about uploading it somewhere and providing a link.
I am trying to parse a OpenBSD image because in parallel of some thesis work, I am experimenting with adding additional parsers to plaso to process OpenBSD-specific data.
Following is information about the partition layout:
$ mmls image.raw
DOS Partition Table
Offset Sector: 0
Units are in 512-byte sectors
Slot Start End Length Description
000: Meta 0000000000 0000000000 0000000001 Primary Table (#0)
001: ------- 0000000000 0000000063 0000000064 Unallocated
002: 000:003 0000000064 0041943039 0041942976 OpenBSD (0xa6)
Even though the partitions are marked as "4.2BSD", they each contain UFS2 file systems.
$ fsstat -o 64 image.raw
FILE SYSTEM INFORMATION
--------------------------------------------
File System Type: UFS 2
Last Written: 2024-04-30 20:51:20 (CEST)
Last Mount Point: /
Volume Name:
System UID: 0
I have also extracted the partition with the BSD disk label (using mmcat image.raw 2 > rec_image.raw) and ran it through plaso with log2timeline -d --storage_file test.plaso ~/Downloads/openbsd/rec_image.raw --partitions all. It created following compressed log file:
2024-08-08 14:22:33,416 [ERROR] (MainProcess) PID:313327 <log2timeline> No supported file system found in source.
If further information is needed, do not hesitate to ask :)
The text was updated successfully, but these errors were encountered:
Describe the problem:
I am using plaso to process a full disk image taken from a OpenBSD virtual machine. As typical for OpenBSD, the disk is split into multiple partitions, each containing some part of the file system.
Plaso only processes data from a single partition. Other partitions are not processed and the respective data is missing in the resulting timeline.
Given the technical details (see additional context below), I think even this processing of the single partition is only due to lucky alignment of partition offsets.
To Reproduce:
The version of Plaso you used:
self-built, based on public commit d3c314d4b5ce004570e13d07c6a9774f107a92ab
The operating system you are running Plaso on (Not the operating system of the image/files you're trying to analyze):
Debian 12
Steps to reproduce the behavior including command line and arguments and output:
running
log2timeline --storage_file test.plaso ~/Downloads/openbsd/image.raw --partitions all
produces a storage file containing info from only the "root" partition of OpenBSD. Following timeline was created withpsort -w timeline.csv test.plaso
timeline.csv
To see that partitions are missing from the processing, notice the lack of data on files under
/var
I am working with a sample disk image of 20GB size. If needed, I can see about uploading it somewhere and providing a link.
The method you used to install Plaso:
pip install -r requirements.txt
python3 setup.py build && python3 setup.py install
Expected behavior:
the expected behavior has two aspects (see additional context for relevant technical details):
Debug output/tracebacks:
running
log2timeline -d --storage_file test.plaso ~/Downloads/openbsd/image.raw --partitions all
produces following compressed log file:
log2timeline-20240808T142736.log.gz
Additional context
I am trying to parse a OpenBSD image because in parallel of some thesis work, I am experimenting with adding additional parsers to plaso to process OpenBSD-specific data.
Following is information about the partition layout:
Even though the partitions are marked as "4.2BSD", they each contain UFS2 file systems.
I have also extracted the partition with the BSD disk label (using
mmcat image.raw 2 > rec_image.raw
) and ran it through plaso withlog2timeline -d --storage_file test.plaso ~/Downloads/openbsd/rec_image.raw --partitions all
. It created following compressed log file:If further information is needed, do not hesitate to ask :)
The text was updated successfully, but these errors were encountered: