Magic¶
Overview¶
The Magic operation attempts to detect various properties of the input data and suggests which operations could help to make more sense of it.
Status¶
| Field | Value |
|---|---|
| Implementation | Partial |
| Parity | Unknown |
| Availability | Available |
| Input requirement | Required |
| Features | none |
| Side effects | [] |
| Deterministic | true |
Input¶
Declared input type: Bytes.
Output¶
Declared output type: JSON. Redirect stdout or use --output-file for exact binary bytes.
Arguments¶
| # | Argument | Type | Required | Default | Allowed | Sensitive | Description |
|---|---|---|---|---|---|---|---|
| 1 | Depth | UnsignedInteger |
no | 3 |
— | no | Maximum number of levels of recursion |
| 2 | Intensive mode | Boolean |
no | false |
— | no | Brute-force XOR, bit rotates, etc. |
| 3 | Extensive language support | Boolean |
no | false |
— | no | Compare byte frequencies to a large number of languages |
| 4 | Crib (known plaintext string or regex) | Regex |
no | <empty> |
— | no | Filter results by matching this string or regex |
Implementation¶
The implementation is in src/operations/magic.rs and declares Bytes input and JSON output. The operation module owns conversion and domain-error rules; registry resolution, argument validation, input-requirement enforcement, tracing, and output validation are performed by rxchef::execution.
Command-line use¶
This operation requires input. Supply literal UTF-8 with --input, exact bytes with --input-file, or pipe bytes on stdin.
rxchef run "Magic" --input-file input.bin --output-file output.bin
Arguments may be supplied positionally in the table order or by name with repeatable --arg NAME=VALUE. Omitted optional arguments use the documented defaults.
Pipeline use¶
Place the operation anywhere a Bytes value is valid. Its JSON result becomes the next step's input. Compact syntax uses the operation name followed by comma-separated arguments; JSON/YAML recipes use an op field and an args array.
Error conditions¶
Schema violations are rejected before the operation runs. Malformed input, unsupported parameter combinations, unavailable optional backends, and domain processing failures produce structured errors and a non-zero CLI status; partial output is never reported as success.
CyberChef compatibility¶
Parity status: Unknown. Unknown records an unassessed compatibility claim; it does not imply equality or incompatibility.
Security considerations¶
Declared side effects: []. Treat parser inputs as untrusted and apply execution limits to large data. Arguments marked sensitive in the schema are redacted from metadata-aware History displays.
Testing evidence¶
Correctness tests: - tests/tests/operations/magic.rs
Performance classification¶
Benchmark evidence: - representative release benchmark
See benchmark results for measured environment and statistics.