Skip to content

fix: install custom crypto engine before pkijs parseInternalValues #44

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Mythie merged 1 commit into from
Mar 5, 2026
Merged

fix: install custom crypto engine before pkijs parseInternalValues #44

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions src/signatures/signers/p12.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -110,6 +110,12 @@ export class P12Signer implements Signer {
options: P12SignerOptions = {},
): Promise<P12Signer> {
try {
// Ensure our custom crypto engine is installed before any pkijs operations.
// pkijs's parseInternalValues() uses the engine internally to decrypt safe
// contents — if they use legacy algorithms (3DES, RC2), the default engine
// will fail with "Unknown contentEncryptionAlgorithm".
getCrypto();

// Ensure we have a proper ArrayBuffer (not SharedArrayBuffer)
const buffer = toArrayBuffer(p12Bytes);

Expand Down