Stas Ukolov

You are right: > Only current user certificates are accessible using this method, not the local machine store. (see [the whole story](https://docs.microsoft.com/en-us/windows/win32/api/wincrypt/nf-wincrypt-certopensystemstorea)). I hope, the way to fetch computer's certificates...

@joper30 It is theoretically possible, but clearly beyond of scope of `win-ca`. One needs more powerful tool for this purpose.

I think, the easiest way is to use [edge] and run `C#` or `PowerShell` script to fetch private key (MSDN provides a log of examples). Unfortunately, [edge] seems unsupported but...

Yes, I'm going to release it today, after passing some tests...

v3.2.2 is on NPM. Please test.

Well. debugging certificate problems can be tricky task. First, I see Websocket is mentioned. This can mean that standard `https` module is *not* used to connect. If so, you can...

Well, certificates with UTF-8 strings is still `terra incognita` in Russia, we strongly prefer to avoid them, using transliteration to Latin-1. So, such errors are very likely to occur and...

I spent some time playing with UTF-8 certificates and that is what I think now: 1. Your PR to node-forge should be cancelled. It changes API so it would break...

Yes, you're right!