WebAssembly port of AES
npm i @hazae41/aes.wasm
- Reproducible building
- Pre-bundled and streamed
- Zero-copy memory slices
- aes
- ctr
- AES-128-CTR-128-BE
import { AesWasm, Memory, Aes128Ctr128BEKey } from "@hazae41/aes.wasm";
// Wait for WASM to load
await AesWasm.initBundled();
const plaintext = new TextEncoder().encode("Hello World")
using memory = new Memory(plaintext)
const key = crypto.getRandomValues(new Uint8Array(16))
const iv = crypto.getRandomValues(new Uint8Array(16))
using key_memory = new Memory(key)
using iv_memory = new Memory(iv)
using cipher = new Aes128Ctr128BEKey(key_memory, iv_memory)
using decipher = new Aes128Ctr128BEKey(key_memory, iv_memory)
/**
* Encryption
*/
cipher.apply_keystream(memory)
console.log(memory.bytes)
cipher.apply_keystream(memory)
console.log(memory.bytes)
/**
* Decryption
*/
decipher.apply_keystream(memory)
console.log(memory.bytes)
decipher.apply_keystream(memory)
console.log(memory.bytes)
You need to install Rust
Then, install wasm-pack
cargo install wasm-pack
Finally, do a clean install and build
npm ci && npm run build
You can build the exact same bytecode using Docker, just be sure you're on a linux/amd64
host
docker compose up --build
Then check that all the files are the same using git status
git status --porcelain
If the output is empty then the bytecode is the same as the one I commited
Each time I commit to the repository, the GitHub's CI does the following:
- Clone the repository
- Reproduce the build using
docker compose up --build
- Throw an error if the
git status --porcelain
output is not empty
Each time I release a new version tag on GitHub, the GitHub's CI does the following:
- Clone the repository
- Do not reproduce the build, as it's already checked by the task above
- Throw an error if there is a
npm diff
between the cloned repository and the same version tag on NPM
If a version is present on NPM but not on GitHub, do not use!