AES-GCM Encrypt / Decrypt Test Tool

Create or read Ymir Tool AES-GCM test payloads with Web Crypto, while retaining a clearly separated legacy CryptoJS compatibility mode.

Modern mode output contract

Modern mode uses AES-GCM with a random salt and IV, derives a key from the passphrase with PBKDF2-SHA-256, and serializes the fields into the versioned ymir-aes-gcm-v1 format. Another application must implement that exact envelope to interoperate.

Random salt and IV mean encrypting the same text twice should produce different payloads.
The authentication tag detects modification or a wrong passphrase.
This browser page is a test utility, not a secret-management system.

Legacy CryptoJS mode

Legacy mode exists only for older CryptoJS passphrase payloads and is intentionally separated from modern AES-GCM. A legacy payload cannot be assumed to contain the same KDF, IV handling, mode, padding, or authentication properties.

Usage boundaries and result checks

AES-GCM Encrypt / Decrypt Test Tool is for this task: Create or read Ymir Tool AES-GCM test payloads with Web Crypto, with a separate legacy CryptoJS compatibility mode. It runs in the browser; start with a short, non-sensitive sample and confirm the behavior before processing more data.

Best use

Use it for a focused AES-GCM Encrypt / Decrypt Test Tool task when a quick browser workbench is appropriate.

Input

text, an encoded string, or the data format named by the tool

Output

an encoded, decoded, or compatibility-check result

Before reuse

For AES-GCM Encrypt / Decrypt Test Tool: Confirm the character set, byte boundary, and target protocol. Encoding is not encryption. See the test method.