Repository navigation
crypto.verify accepted types mismatch documentation (and crypto.sign) #62903
Description
https://github.com/nodejs/node/blob/HEAD/lib/internal/crypto/sig.js#L268
> const { privateKey, publicKey } = require('crypto').generateKeyPairSync('rsa', { modulusLength: 2048 })
> require('crypto').sign('SHA256', new ArrayBuffer(32), privateKey)
> require('crypto').verify('SHA256', new ArrayBuffer(32), publicKey, _)
Uncaught:
TypeError [ERR_INVALID_ARG_TYPE]: The "data" argument must be an instance of Buffer, TypedArray, or DataView. Received an instance of ArrayBuffer
at Object.verifyOneShot [as verify] (node:internal/crypto/sig:261:11) {
code: 'ERR_INVALID_ARG_TYPE'
}Documentation: https://nodejs.org/api/crypto.html#cryptoverifyalgorithm-data-key-signature-callback
Activity
panva commentedon Apr 23, 2026
@ChALkeR i appreciate these scanner found reports, more specifically that you confirm and vet them before posting. Could you possibly make it habit to not post the descriptions as screenshots? It is nearly imposible to engage on mobile.
It also hurts issue search.
ChALkeR commentedon Apr 23, 2026
@panva ack! I initially used text but switched to screenshots because this is more compact on laptop.
Also that part of the info is not that important, these issues always include a non-screenshot explanation (usually title + testcase)
The initial report is auxiliary and I just didn't want to make that too awful to read
I'll switch to spoilers.
crypto: align verifyOneShot accepted types
crypto: align verifyOneShot accepted types
crypto: align verifyOneShot accepted types
crypto: align verifyOneShot accepted types
Merge upstream Node.js v24.18.1 into dotnet/main (#375)