Miroshin Stepan

It lloks like I have to register NO-HASH algorithm https://social.msdn.microsoft.com/Forums/silverlight/en-US/89060f38-d388-4f38-b6e6-4a31271abef3/ecdh-key-agreement-in-cng-how-to-get-the-raw-agreed-secret?forum=windowssecurity


This window is showed when I'm trying to get info about `SecKeyRef` with `SecKeyCopyAttributes` function. I found that there is a `SecAccess` which is used for key creation and determines...

I'm not sure we can test MSCAPI implementation in CircleCI

it looks `SecItemAdd` allows to add `CFDataRef`. [SecItemAdd_osx]( https://opensource.apple.com/source/Security/Security-57740.51.3/OSX/libsecurity_keychain/lib/SecItem.cpp.auto.html)

It works for me in Chrome ``` javascript window.crypto.subtle.generateKey( { name: "RSA-OAEP", modulusLength: 2048, //can be 1024, 2048, or 4096 publicExponent: new Uint8Array([0x01, 0x00, 0x01]), hash: { name: "SHA-1" },...

@pmhatre-swi I will check this and provide a report as soon as possible.

Thanks to today's meeting, I was able to reproduce the error `CryptoServerError: Unrecognized name`. The issue lies in the fact that the current version of Fortify has an outdated implementation...

I have published the updated version of `@peculiar/x509` and updated the script on https://peculiarventures.github.io/fortify-examples/example6.html. The chain is now built using the RSA-PSS algorithm.

I have just updated and published new examples. The chain builder example now logs information about all received certificates from the token into the developer console. Please try it once...