Got Error when updated node-forge package to version 1.3.2

[rjcodedev]

Describe the bug and the expected behaviour When I have updated package to node-forge i have got the error
Invalid`` PKCS#12. macData field present but MAC was not validated.

Is it a bug in signing or in the helpers?

To Reproduce update the package called node-forge to 1.3.2.

[vbuch]

Interesting. I just merged the bump of the version today. No test failed with the new version. https://github.com/vbuch/node-signpdf/pull/297

[rjcodedev]

here are some code snippet which are working perfectly with node-forge 1.3.1

//imports
import { SignPdf } from '@signpdf/signpdf';
import { P12Signer } from '@signpdf/signer-p12';

// buffer of pdf and p12
let PdfBuffer = Buffer.from(req.params.pdfFile, 'base64');
const P12Buffer = Buffer.from(pfxFile, 'base64');

// p12 certificate with it pass phrase
const p12Cert = new P12Signer(P12Buffer, { passphrase: passphrase || null });

// Also i have add placeholder using package '@signpdf/placeholder-pdf-lib' before signing

// Digitally signed pdf
const OBJ = new SignPdf();
const signedpdf = await OBJ.sign(PdfBuffer, p12Cert);

if there any thing you need, please tell me. I am happy to help you @vbuch

[rjcodedev]

hey @vbuch ,

any update on the issue?

[vbuch]

@rjcodedev could you check with 1.3.3? https://github.com/digitalbazaar/forge/blob/main/CHANGELOG.md#133---2025-12-02 https://github.com/digitalbazaar/forge/issues/1127

[rjcodedev]

hey @vbuch ,

The issue has been resolved after updating node-forge package to 1.3.3.

[rjcodedev]

Hey @vbuch,

have you published the latest changes to NPM?

[vbuch]

@rjcodedev https://github.com/vbuch/node-signpdf/compare/master...develop these things are not yet in npm. So the broken 1.3.2 is not there yet as well.

[rjcodedev]

When you are planning to release new changes?