Miroshin Stepan

```js const signedData = new SignedData(); signedData.signerInfos.push(new SignerInfo({ signedAttrs: [ new Attribute({ attrType: "1.2.3.4.5.6", attrValues: [ new Uint8Array([2, 1, 3]).buffer, ] }) ] })); const raw = AsnConvert.serialize(signedData); console.log(Convert.ToHex(raw)); ```...

Method `serialize` doesn't support simple times (eg `number`, `string`, `boolean`, `array`, etc). I think it would be better to add `fromJSON` method to `AsnConvert` class for such cases. ```js AsnConvert.fromJSON(1);...

@Ulterior Thank you. I can reproduce that error This is my app source code ```js const { Crypto } = require("node-webcrypto-p11"); const xadesjs = require("xadesjs"); const fs = require("fs"); const...

I think the problem is in xmldsig and xades implementations. Those modules use Promise instead of async/await. It's hard to find out place where promise works without awaiting. I've created...

xmldsigjs uses `Promise.all`. I think this is why it calls operations in the same time

That script allows to test signing with `asyc/await for..of` and `Promise.all` I tried that script with SoftHSM. It doesn't throw `CKR_OPERATION_ACTIVE` exception ```ts import { Crypto } from "./src"; async...

See https://github.com/PeculiarVentures/xadesjs/issues/84#issuecomment-883999099

#26 Repeates current issue

`@peculiar/webcrypto` use `WeakMap` to protect private key data. Here is [storage implementation](https://github.com/PeculiarVentures/webcrypto/blob/6b304aedf4920f0dfe6bb6504648d1e17948e195/src/mechs/storage.ts). As you can see, `getCryptoKey` throws `Cannot get CryptoKey from secure storage` exception. Sometimes I've got the similar...

> /home/gus/repos/relaynet-internet-gateway/node_modules/@relaycorp/relaynet-core/node_modules/pkijs/build/index.js:3935:19 It's interesting. You've got `node_modules` folder for `@relaycorp/relaynet-core`. I bet the problem is in module duplicates