Miroshin Stepan

[One more example](https://github.com/PeculiarVentures/node-webcrypto-p11/blob/master/lib/cert.ts#L142) Have you seen [node-webcrypto-p11](https://www.npmjs.com/package/node-webcrypto-p11)? It's based on `graphene-pk11` and implements WebCrypto interface.

Yes, you can. [Here](https://github.com/PeculiarVentures/webcrypto-local) is webcrypto-local application which supports multi PKCS#11 libraries. [Here](https://github.com/PeculiarVentures/webcrypto-local/blob/master/src/local/p11_crypto/crypto.ts) you can see code how I use node-webcrypto-p11 and graphene-pk11

`0x80000c01` is a vendor mechanism. You need to register that mechanism in `graphene` first. ```js Mechanism.vendor("CustomName", 0x80000c01); ``` But I think it's an issue. `graphene` must work with a direct...

I opened issue #144 to solve the mechanism problem

@zosocanuck I published the new version. Please try `[email protected]`

@targos Thanks. Waiting for your review.

> Can you please remove the second commit? Done But in my case, it breaks `lint` tests https://github.com/microshine/fast-png/runs/4118047939?check_suite_focus=true

@targos Thank you for the advice. I fixed it

looks like we can fix it by updating [XmlDsigEnvelopedSignatureTransform](https://github.com/PeculiarVentures/xmldsigjs/blob/master/src/xml/transforms/enveloped_signature.ts#L16-L26) ```ts public GetOutput(): any { if (!this.innerXml) { throw new XmlError(XE.PARAM_REQUIRED, "innerXml"); } const signatures = Select(this.innerXml, ".//*[local-name(.)='Signature' and namespace-uri(.)='http://www.w3.org/2000/09/xmldsig#']"); for...

but I've got a problem with NodeJS version. XMLDOM module serializes a bad XML document. It doesn't add a namespace to the second Signature object ### Wrong XML ```xml ```...