Miroshin Stepan

There is the `WixCloseApplications` action in the Win32 installer which (I hope) must close the application ```xml ``` I'll do some tests

@defacto64 Here are some screens of how `WixCloseApplications` works If Fortify is running it shows the next dialog  On `OK` button click without Fortify stopping it shows the next...

@edsono Can you try to update your `~/.fortify/card.json` - update `card.json` - resart Fortify ```json { "cards": [ { "atr": "3BFD1800008131FE4553434536302D43433038312D46C2", "name": "Giesecke & Devrient StarSign USB Token", "driver": "4485A4DCDF92D361F7418D0C447FEC810C609F12"...

This card must be in list. Can you check your `~/.fortify/card.json`? https://github.com/PeculiarVentures/webcrypto-local/blob/master/json/card.json#L243

Cardreader doesn't have linux library https://github.com/PeculiarVentures/webcrypto-local/blob/master/json/card.json#L385-L395 Do you have installed pkcs11 library?

You can update card.json file and restart Fortify application Let me know if it fixes problem. I'll update and publish new `card.json` version

@JanSlabon Can you try to get information about token using [graphene](https://github.com/PeculiarVentures/graphene)? Please check fortify logs. Does Fortify use pkcs11 libs or it uses pvpkcs11 lib for SafeNet tokens?

@JanSlabon Please try this script ```js const graphene = require("graphene-pk11"); function main() { const pathToPkcs11 = "/usr/local/lib/softhsm/libsofthsm2.so"; const softHsm = graphene.Module.load(pathToPkcs11); softHsm.initialize(); try { var slot = softHsm.getSlots(0); console.log(slot.getToken()); }...

I found that we are rewriting a name in `addProvider` function. It uses names from `config.json::providers` and `cards.json` (see Watch pad)  I think we should extend `card.json` and move...

Looks very strange. You don't want to verify the Validity Periods of the Certificate, but use CRLs for path building (which require `checkDate` argument). Would it be easier to build...