Multiple Bombe¶
Overview¶
Emulation of the Bombe machine used to attack Enigma. This version carries out multiple Bombe runs to handle unknown rotor configurations.
Status¶
| Field | Value |
|---|---|
| Implementation | Partial |
| Parity | Unknown |
| Availability | Available |
| Input requirement | Required |
| Features | none |
| Side effects | [] |
| Deterministic | true |
Input¶
Declared input type: String.
Output¶
Declared output type: JSON. Redirect stdout or use --output-file for exact binary bytes.
Arguments¶
| # | Argument | Type | Required | Default | Allowed | Sensitive | Description |
|---|---|---|---|---|---|---|---|
| 1 | Standard Enigmas | String |
no | German Service Enigma (First - 3 rotor) |
— | no | Preset rotor configurations |
| 2 | Main rotors | String |
no | <empty> |
— | no | Newline separated rotor wirings |
| 3 | 4th rotor | String |
no | <empty> |
— | no | Newline separated 4th rotor wirings |
| 4 | Reflectors | String |
no | <empty> |
— | no | Newline separated reflector pairs |
| 5 | Crib | String |
no | <empty> |
— | no | Known plaintext |
| 6 | Crib offset | Integer |
no | 0 |
— | no | Offset of the crib in the ciphertext |
| 7 | Use checking machine | Boolean |
no | true |
— | no | Whether to use the checking machine |
Implementation¶
The implementation is in src/operations/multiple_bombe.rs and declares String 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 "Multiple Bombe" --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 String 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/multiple_bombe.rs
Performance classification¶
Excluded from the committed representative benchmark set: No stable representative benchmark case is defined; operation remains Partial until performance evidence is reviewed.