Difference between revisions of "How Truxton Works"
| Line 5: | Line 5: | ||
We will not give an overview of the design of the Truxton Architecture. | We will not give an overview of the design of the Truxton Architecture. | ||
| − | = | + | =Load= |
Someone has decided that they have data that needs Truxton exploitation. | Someone has decided that they have data that needs Truxton exploitation. | ||
Let's say it is a hard drive image in the popular E01 format, ''Bob.E01'' | Let's say it is a hard drive image in the popular E01 format, ''Bob.E01'' | ||
Revision as of 12:09, 10 June 2020
Truxton was designed to exploit data in a scalable way. You can add more exploitation processes on your loader machine or you can add more machines to the exploitation process.
This article will walk you through the path data takes through Truxton. We will not give an overview of the design of the Truxton Architecture.
Load
Someone has decided that they have data that needs Truxton exploitation. Let's say it is a hard drive image in the popular E01 format, Bob.E01
The entry into Truxton is the Load process.
load.exe T:\Bob.E01
Load will open the file, determine what type it is and navigate it. Load's purpose in life is to find files, identify their type, eliminate their contents based on known-good MD5 hashes, put the meta-data about the file into a database, contents into a depot, then send messages to other ETL processes that have registered to receive that type of file.
