The fortify-tools from peculiarventures

Disable `Create new` button for read only providers

ws.info()
  .then(info => console.log(info))
  .catch((err) => {console.log(err)})

Update certificate view to be consistent with certnod

You made some improvements to the certificate view, they should find their way back here.

Add App Error Boundary Component

Javascript error after entering YubiKey PIN

The following error surfaces when entering the YubiKey PIN.

Looks like it would be caused by this recent commit:

a072594#diff-82612db8f32ac3ab655fc3ee29a1e9334c9c22aae60de4ff0dba8d4b5b6c2b67R488

See screenshots below.

Fortify version: 1.3.4
OS: Windows
Browser: Chrome Version 91.0.4472.124 (Official Build) (32-bit)

Add `extractable` checkbox

WebCrypto API allows to generate keys with extractable parameter. We need UI checkbox for this parameter

Add a new FAQs to Fortify web page

What are the privacy implications of using Fortify?
Websites that you visit will be able to discover that you are running Fortify and this might be useful when combined with other information your browser leaks to track you on the web. These websites will not be able to tell what certificates, or smart cards you have unless you authorize them.

Once you authorize a website it will be able to see what certificates you have, with that information they may be able to infer other information about you. For example, if your certificates contain your legal name, they will have access to that information or if you have a national id card with a certificate it may be able to infer your citizenship.

What are the security implications of using Fortify?
We have gone out of our way to try to make Fortify a secure solution. We do believe the solution is well designed and resilient but to err is human so we expect to have security issues to resolve in the future.

With that said, the nature of the feature goals of Fortify requires it to enable websites to interact with the X.509 certificates and their associated cryptographic keys. This means when you grant these websites access to use Fortify they will have an opportunity to use those certificates and keys.

For smart cards Fortify will only let you use certificates that require a pin on use, it also has a unique session to the smart card per website so you will be prompted for use.

For software protected keys however if the software implementation does not require a prompt or pin on use the website will be able to use the associated key without explicit consent.

You should also be mindful if a website uses Fortify, any third-party origins the website incorporates will also be able to use Fortify.

How do I decide what websites I should let use Fortify
You should only let websites use Fortify that you trust, this is because they may be able to track you (like a cookie) and potentially trick you into signing something with a cryptographic key you control.

Add tests

Server is offline. Wait until the connection is established

Hello,

After running fortify-web with npm run start, the server run but i always have on start the dialog modal with "Server is offline. Wait until the connection is established",
how i can fix that to run fortify properly,

thanks,

Spanish: " CIÓN DE CLAVE PÚ" -> "INFORMACIÓN DE CLAVE PÚBLICA"

Fortify app not running on Windows 7 (32-bit) Virtual Machine

On a Windows 7 (32-bit) virtual machine, hosted by VMware Workstation, the Fortify app does not run.
Trying to run it causes the following error message to appear:

Create App Sidebar component

Add Provider list
Add app logo
Add footer texts

Add skeleton loader for providers list

Design
Add component

Yubikey provider not being recognized?

I'm new to fortify & yubikey tooling; and exploring the capabilities of this application. Here's what I've done so far.

I have tested the yubikey and it appears to work correctly. I have also ran yubikey-piv-tool and able to read certificates; ie yubico-piv-tool -s 9(a|c|d) --action read-certificate and it comes back with the certificates. Yubikey manager appears to functioning correctly.

When I launch the Fortify Tools the only providers that show up are Mac Crypto & NSS Certificate DB. The Yubikey provider does not show up. I have tested this with firefox & chrome and the same results.

I looked into the ~/.fortify/config.json. Everything looks vanilla.
In ~/.fortify/card.json; I see

{
"id": "993988460d8f49a2ac519a2935f00533",
"name": "YubiKey",
"file": {
"osx": "/usr/local/lib/libykcs11.dylib",
"linux": "/usr/local/lib/libykcs11.so",
"windows": "%WINDIR/System32/libykcs11-1.dll"
}
},

I've confirmed that the dylib is in the matching location:

$ ls -talr /usr/local/lib/libykcs11.dylib
lrwxr-xr-x 1 root wheel 17 Jul 3 17:15 /usr/local/lib/libykcs11.dylib -> libykcs11.2.dylib

Any idea on next steps to look at to try to figure out why the Yubikey provider is not showing up? I've tried to follow all the documentation/postings I could find to debug; what am I doing wrong?

Add support for Spanish National Identification Card (DNIe)

Reader name: C3PO USB SMART CARD READER 0
ATR: 3B7F960000006A444E4965200101550410039000

{
   "cards": [{
   	"atr": "3B7F960000006A444E4965200101550410039000",
   	"name": "Token name",
   	"driver": "F87A559DAFC9D182D9114BFDF7158E986F34B8C8"
   }],
   "drivers": [{
   	"id": "F87A559DAFC9D182D9114BFDF7158E986F34B8C8",
   	"name": "Driver name",
   	"file": {
   		"windows": "path/to/pkcs11.dll",
   		"osx": "path/to/pkcs11.dylib"
   	}
   }]
}

Smart card ATR parsing 3B7F960000006A444E4965200101550410039000

Impossible to skip PIN entering

The application shows a PIN dialog if the token requires login. On Cancel button click it prompts PIN entering again and again

Add support for '3bdf18008131fe580031b964050e010073b401d300000022' token

Reader name: Gemalto USB Smart Card Reader 0
ATR: 3BDF18008131FE580031B964050E010073B401D300000022

{
   "cards": [{
   	"atr": "3BDF18008131FE580031B964050E010073B401D300000022",
   	"name": "Slovak eID",
        "readOnly": true,
   	"driver": "39798896FC5DD6E2A96989718F694334275E0EAC"
   }],
   "drivers": [{
   	"id": "39798896FC5DD6E2A96989718F694334275E0EAC",
   	"name": "Slovak eID",
   	"file": {
   		"windows": {
                      "x86": "%PROGRAMFILES(X86)/eID klient/pkcs11_x64.dll",
                      "x64": "%PROGRAMFILES(X86)/eID klient/pkcs11_x86.dll"
                },
                "linux": {
                      "x86": "/usr/lib/eidklient/libpkcs11_sig_x64.so",
                      "x64": "/usr/lib/eidklient/libpkcs11_sig_x86.so"
                },
   		"osx": "/Applications/eIDklient.app/Contents/Pkcs11/libPkcs11.dylib"
   	}
   }]
}

Smart card ATR parsing 3BDF18008131FE580031B964050E010073B401D300000022

Update certificate creation logic

PVPKCS11 which uses minidrivers for SmartCards cannot import certificate to token without private key. We need to add cert to token in the next order

set private key
set public key (optional)
set certificate

Add linux to the fortify web page

Create App layout

Add Theme & configuration

ERROR: providers.where(...).get is not a function

config.json

Without $HOME/.pki/nssdb it works without error

{
  "locale": "en",
  "providers": [
    {
      "lib": "/usr/local/lib/softhsm/libsofthsm2.so",
      "slots": [
        0
      ]
    },
    {
      "lib": "/usr/local/opt/nss/lib/libsoftokn3.dylib",
      "slots": [
        1
      ],
      "libraryParameters": "configdir='/Users/microshine/tmp/nss' certPrefix='' keyPrefix='' secmod='' flags= updatedir='' updateCertPrefix='' updateKeyPrefix='' updateid='' updateTokenDescription='NSS#0' dbTokenDescription='NSS#1' cryptoTokenDescription='NSS#2' tokenDescription='NSS#3' "
    },
    {
      "lib": "/usr/local/opt/nss/lib/libsoftokn3.dylib",
      "slots": [
        1
      ],
      "libraryParameters": "configdir='$HOME/.pki/nssdb' certPrefix='' keyPrefix='' secmod='' flags= updatedir='' updateCertPrefix='' updateKeyPrefix='' updateid='' updateTokenDescription='NSS#0' dbTokenDescription='NSS default'"
    }
  ],
  "logging": true
}

Error

error.js:78 ERROR MESSAGE: TypeError: providers.where(...).get is not a function
    at providerSelect$ (index.js:406)
    at tryCatch (runtime.js:65)
    at Generator.invoke [as _invoke] (runtime.js:303)
    at Generator.prototype.(:3000/certificate/anonymous function) [as next] (webpack:///./~/babel-polyfill/~/regenerator-runtime/runtime.js?:117:21)
    at next (proc.js:313)
    at currCb (proc.js:389)
    at runSelectEffect (proc.js:699)
    at runEffect (proc.js:436)
    at next (proc.js:317)
    at proc (proc.js:272)

Update Vite & React to latest

Update FAQ to include Ubuntu

Yubikey provider listed twice

Sometimes after fortify has been running for some time, it will list two providers in the fortify tools provider drop-down as though there are two Yubikeys plugged in when there is definitely only one.

This will then lead to errors in trying to perform operations with the certificates on the card.

Usually have to restart Fortify to resolve this.

Fortify version 1.3.4 running on macOs Catalina 10.15.4

Add ESLint

Add ESLint
Add Prettier

Create CertificatesList component

Create CertificatesProvidersList component

I should be able to type in country field to select country

Moved from PeculiarVentures/fortify#91

Update behavior on token events

I'm updating Fortify. New version can return more than 1 info about added or removed tokens. Current version of UI shows only 1 item from the list

After 2 tokens insertion

Provider:Token Amount of tokens was changed (+2/-0)

After window refreshing

@donskov if you need updated Fortify version let me know about it

Create FetchingStatusOwerlay component

Component added but dialogs still need texts & styling

Styling:

Stories:

Add vitest

Add post css, autoprefixer, clsx, scss

Add Certificate Viewer

Not clear why buttons are disabled

Suggestions:

Add tooltip This is a read-only token so this operation is disabled.
Show information about the token which says that it's in read-only mode and hide edit buttons

@alexgbv Could you suggest a UI solution?

Error occurs: `Unhandled Rejection (ReferenceError): WebcryptoSocket is not defined`

An error occurs when running fortify-web in my local environment.

git clone https://github.com/PeculiarVentures/fortify-web.git
npm install
npm run start
Browser automatically opens http://localhost:3000
then error occurs on browser

*Enviroment
Windows10:
node version: v12.17.0
npm version: 6.14.4

Cannot read property 'generateKey' of undefined

Hiya Guys,

When I try to initialize fortify web everything works fine on a 127.0.0.1 connection as soon as I deploy it to our internal website i get the error message "Cannot read property 'generateKey' of undefined".

Could it be that this error comes because there is no SSL certificate on it and just uses plain old http?