Miroshin Stepan

The problem is related to **fixed buffer allocation** in the `graphene-pk11` library used by `node-webcrypto-p11`. ### Root Cause In the [`src/crypto/sign.ts`](https://github.com/PeculiarVentures/graphene/blob/8993efa714597e88f99a88e9748707cbd5419ea1/src/crypto/sign.ts) file, **hardcoded 1024-byte buffers** are used for all signing...

It seems the error is coming from the provider being used. It's likely that SoftHSM is not configured properly, or the configuration file might be missing. To understand the issue,...

@Inso2008 Can you enable log using Fortify Preferences, restart Fortify, sign document and share the Fortify log?

As I can see from the logs, the error occurs at the moment of signing the data using the RSASSA-PKCS1-v1_5 mechanism in combination with SHA-256. During the signing process, the...

Based on the logs, there seems to be a problem with how a key is being used: ``` ERROR C_Sign Exception: NTException: NTException(0x80090029) NCryptSignHash The requested operation is not supported....

Actually, the @peculiar/x509 library does support generating x509 certificates from a Certificate Signing Request (CSR) and a Certificate Authority (CA) certificate. Here’s an example to illustrate how you can achieve...