Rabbit Stream Cipher Tool

⚙️ Core Structure

• Key length: 128 bits (16 bytes), fixed
• IV length: 64 bits (8 bytes), optional
• Internal state: 512 bits (8 × 64-bit variables)
• Counter system: 8 × 32-bit counters
• ARX structure: addition, rotation, XOR
• Output: 128 bits (16 bytes) per iteration

🔄 Workflow

• Initialization:Use the key to initialize the internal state and counters
• IV setup:If an IV is used, perform additional state mixing
• Iteration function:Update the counters and state variables
• Extraction function:Extract the keystream from the internal state
• Encryption:XOR the keystream with the plaintext
• Decryption:XOR the keystream with the ciphertext (the same operation)

🏆 Project Overview

eSTREAM(ECRYPT Stream Cipher Project) is a stream cipher call for proposals launched by the European ECRYPT network, similar to the AES call for proposals.

• Start date: 2004
• Completion date: 2008
• Goal: identify new stream ciphers suitable for widespread use
• Categories: software performance, hardware performance
• Participants: top cryptographers worldwide

✅ Final Recommended Algorithm

Software performance category (3):

• Rabbit - Ultra-high performance
• Salsa20/12 - Simple and secure
• HC-128 - Large state space

Hardware performance category (4):

• Grain v1
• MICKEY 2.0
• Trivium

⚠️ Scenarios to Consider

• Strict compliance requirements:Some industry standards may only recognize AES
• Hardware acceleration available:When AES-NI is available, AES may be faster
• Requires authenticated encryption:Rabbit needs to be combined with an additional MAC
• Critical infrastructure:Prefer the more widely vetted AES
• Long-term data protection:AES-256 may be safer

✅ Recommended Practice

• Evaluate the performance and security requirements of the specific scenario
• Consider whether hardware acceleration is needed
• Check industry compliance requirements
• Use in combination with a MAC algorithm such as HMAC
• Conduct actual performance benchmark comparisons
• Keep key management secure

🐰 Choose Rabbit

• PursuingUltimate performance(especially 32-bit systems)
• Very resource-constrained environments
• Systems that already integrate Rabbit
• Internal applications that do not require broad interoperability
• No strict standardization requirements

🌊 Choose ChaCha20

• RequiredHigher security margin(256-bit key)
• Requires authenticated encryption (ChaCha20-Poly1305)
• Requires IETF standard support (RFC 8439)
• Standard protocols such as TLS and VPN
• High cross-platform interoperability requirements
• Used by major companies such as Google and Cloudflare

🔑 Key Management

• Use a cryptographically secure random number generator (CSPRNG)
• Use a different key for each session
• Keys should be stored and transmitted securely
• Consider using a key derivation function (KDF)
• Rotate keys regularly

🔐 IV Usage (if supported)

• Use a new random IV for each encryption
• The IV can be public but must not be reused
• The IV should be stored/transmitted together with the ciphertext
• Do not use a predictable IV

✅ Authenticated Encryption

• Rabbit provides confidentiality only, not integrity
• Should be used with a MAC such as HMAC-SHA256
• The Encrypt-then-MAC mode is recommended
• Or consider using ChaCha20-Poly1305 (built-in authentication)

⚠️ Common Mistakes

• ❌ Reusing the same keystream (repeating the key+IV combination)
• ❌ Does not verify ciphertext integrity
• ❌ Using weak keys or simple strings
• ❌ Storing keys on the client
• ❌ Does not consider side channels such as timing attacks