cosmology-compat

@decryption/cosmology-compat

Deprecated by design. This package exists so data written by the cosmology CLI stays readable. Do not use it to encrypt anything new — use @decryption/core instead.

Why it is weak

The old scheme was CryptoJS.AES.encrypt(text, SHA256(salt).toString()), which means:

• keys derived with OpenSSL EVP_BytesToKey — MD5, a single iteration, no work factor;
• AES-256-CBC with no authentication tag, so tampering is undetectable;
• a wrong passphrase yields an empty string in CryptoJS rather than an error.

This package reimplements the format byte-for-byte on top of @decryption/ciphers (no crypto-js dependency), and turns the silent-failure case into a thrown WrongPassphraseError.

Usage

import { decrypt, decryptWithEncryptedSalt, upgradeEnvelopeToString } from '@decryption/cosmology-compat';

// Single-layer blobs
const plaintext = decrypt(salt, oldCiphertext);

// The demo's two-layer scheme (encrypted salt wrapping the real salt)
const mnemonic = decryptWithEncryptedSalt(salt, encryptedSalt, encryptedWallet);

// One-way door onto the modern format
const modern = upgradeEnvelopeToString(oldCiphertext, salt, newPassphrase);

Raw CryptoJS compatibility, if you have blobs that never went through @cosmology/core:

import { cryptoJsEncrypt, cryptoJsDecrypt } from '@decryption/cosmology-compat';

cryptoJsDecrypt(base64Ciphertext, passphrase); // throws instead of returning ''

Verified compatibility

The test suite encrypts with the real crypto-js package and decrypts with this one (and vice versa), so the byte compatibility claim is checked on every run rather than assumed.