Ryan Hurst

@Root-Core it definitely works on Windows, we re-wrote it specifically to remove a dependency that was causing issues with working on Windows and have tested it there extensively. Getting it...

@hildjj no, not yet. I will talk to him tomorrow.

I was a bit over zealous with copy and paste, the goal is to have generated documents. If the Docdash theme will not work we have some guys we can...

Agreed, was hoping you might be able to provide assurance it was OK :)

Yes you should be able to patch any application that uses node-webcrypto-owl to use the native implementation instead.

To do this we will need to switch to BorringSSL which is something I want to see us do anyway.

A new mechanism was recently added in a PR, the test failure in CI has no relation to this issue here it seems. Hopefully, https://github.com/PeculiarVentures/graphene/commit/51ff1b7c4c0fadbaec1cba2f123f550757029d97 will fix it.

There is a new change in the graphene-cli and it should make this work, see - https://github.com/PeculiarVentures/graphene-cli/issues/5 We will need to update the capabilities documents for each document.

@jspark311 can you see if this fixes your issue with the NitroKey?

@nickrmc83 would you be able to re-run the Thales capabilities?