Rabbit

Overview

Rabbit is a high-speed stream cipher introduced in 2003 and defined in RFC 4503.

The cipher uses a 128-bit key and an optional 64-bit initialization vector (IV).

big-endian: based on RFC4503 and RFC3447
little-endian: compatible with Crypto++

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: String. Redirect stdout or use --output-file for exact binary bytes.

Arguments

# Argument Type Required Default Allowed Sensitive Description
1 Key Bytes yes <empty> yes 128-bit key
2 IV Bytes no <empty> no 64-bit IV
3 Endianness String no Big no Big or Little
4 Input String no Raw no Raw or Hex
5 Output String no Raw no Raw or Hex

Implementation

The implementation is in src/operations/rabbit.rs and declares String input and String 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 "Rabbit" --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 String 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/rabbit.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.

References