Miroshin Stepan

We've got successful tests for `C_Sign` function on [CircleCI](https://travis-ci.org/PeculiarVentures/pkcs11js/jobs/585442098#L1716) ### CircleCI System ``` OS: Ubuntu 16.04.6 LTS NodeJS: v8.16.1 pkcs11js: 1.0.19 PKCS#11: SoftHSMv2 ```

I can reproduce this exception locally. I'll fix this problem

What PKCS#11 library do you use? Looks like we had got a Segmentation fault before https://github.com/PeculiarVentures/pkcs11js/issues/47 Here is an output of the segmentation fault stack trace ``` Error: signal 11:...

Please try signing on https://peculiarventures.github.io/fortify-examples/example5.html and https://codesandbox.io/s/fortify-demo-2b9x8

@DanialHuckabee Fortify uses `node-webcrypto-p11` module Please try this code it must point to the problematic attribute ```js const { Crypto } = require("node-webcrypto-p11"); const library = "/path/to/your/pkcs11.dll"; async function getPrivateKeyAsync(crypto,...

I think the problem is in public exponent or modules getting for private key algorithm

You can add your token to Fortify config file `~/.fortify/config.json`. Please don't forget to restart your Fortify application. ### Example ``` { "locale": "en", "logging": true, "cards": [ { "atr":...

 You can enable logging and get a detailed exception message

> I am using pkcs11js inside an Angular Electron application Can you share a part of your source code where you are using `pkcs11js` It's interesting to see which mechanisms...

try to increase buffer for a signature object to 1024