Vault 7: Projects

This publication series is about specific projects related to the Vault 7 main publication.

SECRET//20350112
9. Must acquire/build toolchain to build Flytrap software modules for the correct
processor.
10. Must be able to reassemble image, including manufacturer’s headers and trailers.
This typically requires some reverse engineering. Headers/Trailers typically
include lengths, dates, CRCs, versions, magic strings, etc. in various formats.
15.5.2 (U) Parameters That Must Be Decided Before Forming an Image
(S) When building a firmware, a number of parameters must be built directly into the
image, and as such, must be decided upon before the Image Formation process. These
parameters are specified in a configuration file named (flytrap.config). Here are the
pertinent parameters:
Up to 5 Initial Beacon Addresses/Ports (see 15.2)
Initial Beacon Interval in seconds (see 15.2)
Initial Beacon Traffic Requirement (see 15.2)
Initial Beacon Traffic Requirement Timeout in seconds (see 15.2)
Initial Beacon Fast Retry Interval in seconds (see 15.2)
Initial Beacon Number of Fast Retries (see 15.2)
Initial Beacon Slow Retry Interval in seconds (see 15.2)
Encryption type (64-bit Blowfish or 128-bit AES) – typically 64-bit Blowfish
Enable Firmware Inhibit (see 5.2.3.18)
Enable VPN support (see 5.2.3.9.3)
Include Telnet Daemon - “no” for release images – see 15.6
Include Netcat – typically “no” for release images
Enable Debug Printing – “no” for release images – “yes” enables Flytrap
software printing of debug information (useful for development, testing, and
diagnostics – see 15.6)
(S) NOTE: the flytrap.config file contains documentation on each of the features and
should be regarded as the most up-to-date and correct documentation source.
138
SECRET//20350112

e-Highlighter

Click to send permalink to address bar, or right-click to copy permalink.

Un-highlight all Un-highlight selectionu Highlight selectionh