Miroshin Stepan

EC key doesn't have modulus. Use algorithm parameters to get information about named curve. Try to use `ECPublicKey.namedCurve`  For that public key KeyChain shows key size 256bits

You don't need to use `@peculiar/webcrypto` for the browser. Use global `crypto` object. ```js self.crypto.subtle.verify(...); ``` As I can see it throws exception [here](https://github.com/PeculiarVentures/webcrypto/blob/7a3f11f3fd7df282084ce377d4be2e3b8b7ac118/src/mechs/ec/crypto.ts#L51). It calls NodeJS Crypto API. But...

Looks like your project uses multiple versions of @peculiar/asn1-schema. Please deduplicate dependences and try again

Looks like you've got a few versions of `@peculiar/asn1-schema` in your project. Call `npm list @peculiar/asn1-schema` to check it out. And `npm dedupe` to fix it

`webcrypto` is based on NodeJS `crypto` API. The minimum version of NodeJS must be v10. But electron doesn't implement all NodeJS crypto API (etc. `generateKeys`). This is why I use...

@yalamber You must put `libeay32.dll` near `nodessl.node` (`node-webcrypto-oss/build/Release`) or `electron.exe`

@yalamber you can take prebuild openssl here https://github.com/PeculiarVentures/fortify/releases

I'm using NodeJS v14.5.4 and I don't have the error. Could you share `package.json` file to reproduce that error? `@peculiar/webcrypto` uses `engine` option. It uses NodeJS Crypto API which was...

@gnarea I think the simplest way is creating and registering the new AES-KW provider with extra dependency for Electron. I don't think it's a good solution to import such dependencies...

> We could even just extend the AesKwProvider class from this project and only override onEncrypt()/onDecrypt(), right? It's impossible. `@peculiar/webcrypto` doesn't export any providers. > I can put a PR...