microsoft / go-crypto-winnative Goto Github PK

I noticed these when I was doing a test run with the CNG backend in microsoft/go (and got a little confused how I'd ended up unning the OpenSSL backend on Windows 😄):

And I searched for OpenSSL and saw this, too:

I think the first one just needs to be updated, but with the second one I'm not sure if it's the same between OpenSSL and CNG.

@qmuntal I've found some Go code to unmarshal an RSA public key, but I need similar code to unmarshal the output of NCryptExportKey to an rsa.PrivateKey instance. I am a novice in this area so some guidance would be appreciated!

This issue lists the algorithms that are implemented in dev.boringbranch by BoringSSL but not available in Windows CNG.

• SHA methods don't implement BinaryMarshaller and BinaryUnmarshaller interfaces. I still haven't found a way to get the inner state of the SHAs and map it to Go binary representation.
• SHA224.
• MD5SHA1
• AES and DES CTR mode. We might be able to implement it using AES in ECB mode and some custom logic: https://gist.github.com/hanswolff/8809275. Another option is to fallback to Go Crypto.
• rsa.PSSSaltLengthAuto
• RSA keys with more than 2 primes
• RSA key lengths are more restrictive, i.e. must be bigger or equal than 512 and multiple of 8.
• dsa.L2048N224