@jscrypto/kdfs

KDF components for @jscrypto/core.

Demo

• PBKDF2 Online
• EvpKDF Online
• HKDF Online
• Scrypt KDF Online
• Argon2 KDF Online

Components

• PBKDF2
• EvpKDF
• HKDF
• Scrypt
• Argon2

import { createRegistry } from '@jscrypto/core';
import { pbkdf2 } from '@jscrypto/kdfs/pbkdf2';

const registry = createRegistry().use(pbkdf2);

Each KDF group also exports a preset:

import { hkdfPreset } from '@jscrypto/kdfs/hkdf';
import { pbkdf2Preset } from '@jscrypto/kdfs/pbkdf2';

registry
  .use(pbkdf2Preset)
  .use(hkdfPreset);

Use classicKdfsPreset() to register the classic compatibility set: PBKDF2 and EvpKDF.

Use kdfsPreset() to register the full KDF package set, including HKDF, HKDF-Extract, HKDF-Expand, Scrypt, and Argon2.

Browser

For browser apps, prefer @jscrypto/suite/basic plus independent KDF/hash bundles instead of the full @jscrypto/kdfs bundle:

<script src="jscrypto-core.iife.min.js"></script>
<script src="jscrypto-suite-basic.iife.min.js"></script>
<script src="jscrypto-hashes-sha256.iife.min.js"></script>
<script src="jscrypto-kdfs-hkdf.iife.min.js"></script>
<script>
  jscryptoSuiteBasic.registry
    .use(jscryptoHashesSha256.sha256Preset)
    .use(jscryptoKdfsHkdf.hkdfPreset);
</script>

The package still provides @jscrypto/kdfs/browser as a full convenience bundle, but size-sensitive browser builds should load the specific subpath bundle they need.