Skip to content

Commit a13ff55

Browse files
committed
docs/analysis: add hint on magic bytes
Signed-off-by: Daniel Maslowski <[email protected]>
1 parent 419b03d commit a13ff55

File tree

1 file changed

+9
-2
lines changed

1 file changed

+9
-2
lines changed

docs/analysis.md

Lines changed: 9 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,14 @@ The following example shall help understanding the thought process when trying
1212
to get behind the meaning of unknown data. Mind that this takes a lot of time.
1313
It often starts with the simple question: What is this?
1414

15+
A first helpful step is to try to identify headers and formats. Binary data
16+
structures often start with markers called signatures, _magic_ bytes or numbers,
17+
commonly four ASCII characters or significant numbers that suggest a meaning.
18+
There are tools such as `file` to recognize them, as well as lists of common
19+
[file signatures](https://en.wikipedia.org/wiki/List_of_file_signatures) and
20+
[magic bytes](https://tool.lu/en_US/magicbytes/). Search engines and communities
21+
are quick to assist with a first effort.
22+
1523
Often enough, other researchers have already performed initial work to build on
1624
top of. In the case of Intel ME generation 3 hardware, there are manifests with
1725
lots of metadata, described through what are called _extensions_ by Positive
@@ -128,6 +136,5 @@ Which yields:
128136
514:d=0 hl=2 l= 0 prim: EOC
129137
```
130138

131-
Success! Next up, we need to find a suitable library to parse this data. Further
139+
Success! Next up, we need to find a suitable library to parse this data. Further
132140
development is omitted here.
133-

0 commit comments

Comments
 (0)