Miroshin Stepan

`@peculiar/webcrypto` uses internal `getCryptoKey`/`setCryptoKey` functions which allow to protect private key blobs of NodeJS keys. Without those blobs, you can't export NodeJS keys to the extra crypto module. This is...

Here are two representations of the one key. `CryptoKey` doesn't keep a private blob of NodeJS secret key.  `getCryptoKey` function allows getting `AesCryptoKey` with the private NodeJS secret key...

Here is the package structure 

I've got the same security notification ``` └─┬ [email protected] └─┬ [email protected] └─┬ [email protected] └── [email protected] ``` 

Sorry for my late response. I've reviewed the information and logs you provided and noticed the following points. Your screenshot shows the site tools.fortifyapp.com, but it's using 'Windows CryptoAPI' as...

Upon further analysis of the Fortify application, I've managed to replicate a similar issue. I have opened a separate ticket at https://github.com/PeculiarVentures/webcrypto-local/issues/281 that details the identified problem. To prevent this...

@RafaelAban After using the PKCS#11 session, it's recommended to end it, which helps secure the use of this session across different domains. In addition to the `login` method, the crypto...

I've updated the `card.json` file. `@webcrypto-local/[email protected]` includes `SafeNet eToken 5300` token. @donskov please publish the `card.json` file for Fortify app.

Hi @JanSlabon `@peculiar/x509` and `PKIjs` can not verify the signature too. Looks like `Windows CryptoAPI` provider works incorrectly. I'll check it out

The issue might stem from the SafeNet eToken 5110+ CC (940B) not supporting key creation through the C_CopyObject, which is employed by the `crypto/keyStorage/setItem` method. Try setting the `token: true`...