Difference between revisions of "Poly"
(Created page with "{| style="float:right;border:1px solid black" |+ Details | Executable | <code>Poly.exe</code> |- | Stage | style="text-align:center;" | 6 |- | Percent Complete | style="text-a...") |
|||
| (4 intermediate revisions by the same user not shown) | |||
| Line 5: | Line 5: | ||
|- | |- | ||
| Stage | | Stage | ||
| − | | style="text-align:center;" | | + | | style="text-align:center;" | 32 |
|- | |- | ||
| Percent Complete | | Percent Complete | ||
| − | | style="text-align:center;" | | + | | style="text-align:center;" | 60% |
|- | |- | ||
| Message Queue | | Message Queue | ||
| − | | <code> | + | | style="text-align:center;" | <code>poly</code> |
|} | |} | ||
| − | + | Poly is responsible for coordinating the expansion of data that resides across more than a single file. | |
| + | It does not perform the actual expanding of the files. | ||
| + | Poly is the first step in the [[ETL Stages#Semi-Chaotic|semi-chaotic]] stage of media exploitation. | ||
| + | Files produced here trigger more [[ETL Stages#Chaos|chaos]] that [[Les]] must figure out. | ||
| + | |||
| + | There should be only one instance of Poly running on the network. | ||
| + | |||
| + | =Details= | ||
| + | |||
| + | During initialization, ETLs that know how to expand multi-file data, like a [[Type_Spanned_Zip|spanned zip archive]], will register themselves with Poly. | ||
| + | This registration is merely a [[File_Types_Supported|file type]] and a [[Message Bus|message queue name]]. | ||
| + | |||
| + | When [[Les]] sees that files in a given media are no longer being processed in the [[ETL Stages#Chaos|free-for-all]] initial stages of exploitation, it will notify Poly. | ||
| + | Upon receiving this notification, Poly will query that media for the registered file types and notify the appropriate ETLs. | ||
| + | If [[Les]] sees that no new files were produced or Poly had nothing to do, it will advance the media to the stage following Poly, normally this is [[Stitch]]. | ||
=File Types= | =File Types= | ||
| − | + | Poly processes the following types of files. | |
{| class="wikitable" | {| class="wikitable" | ||
| Line 24: | Line 38: | ||
! Produces | ! Produces | ||
|- | |- | ||
| − | | [[ | + | | [[Type_Spanned_Zip]] |
| Files | | Files | ||
|- | |- | ||
| − | | [[ | + | | [[Type_SQLite_Write_Ahead_Log]] |
| Files | | Files | ||
|- | |- | ||
| − | | [[ | + | | [[Type_SRUM_Database]] |
| − | | | + | | [[Event Table|Events]] |
| + | |- | ||
| + | | [[Type_Office_Telemetry_Event]] | ||
| + | | [[Event Table|Events]] | ||
|} | |} | ||
Latest revision as of 12:55, 25 January 2021
| Executable | Poly.exe
|
| Stage | 32 |
| Percent Complete | 60% |
| Message Queue | poly
|
Poly is responsible for coordinating the expansion of data that resides across more than a single file. It does not perform the actual expanding of the files. Poly is the first step in the semi-chaotic stage of media exploitation. Files produced here trigger more chaos that Les must figure out.
There should be only one instance of Poly running on the network.
Details
During initialization, ETLs that know how to expand multi-file data, like a spanned zip archive, will register themselves with Poly. This registration is merely a file type and a message queue name.
When Les sees that files in a given media are no longer being processed in the free-for-all initial stages of exploitation, it will notify Poly. Upon receiving this notification, Poly will query that media for the registered file types and notify the appropriate ETLs. If Les sees that no new files were produced or Poly had nothing to do, it will advance the media to the stage following Poly, normally this is Stitch.
File Types
Poly processes the following types of files.
| File Type | Produces |
|---|---|
| Type_Spanned_Zip | Files |
| Type_SQLite_Write_Ahead_Log | Files |
| Type_SRUM_Database | Events |
| Type_Office_Telemetry_Event | Events |
