Adding SymCrypt as a crypto provider

[juliusl]

Hello, I have a fork where I've added support for SymCrypt as a crypto provider - so far it seems to work w/ the tests in the repo as well as another project I'm working with as a drop-in replacement.

Since it would be adding a new crypto provider, I wanted to file an issue to see if this something this project would be open to before putting up a PR.

[cpu]

I haven't given this deep thought yet, but my initial instinct is that we should consider following the rustls approach of making it possible for code external to the library to provide its own cryptography provider of choice and not bundling more options as built-in features.

[djc]

Yup, I think so too.

[est31]

We have botan as a builtin backend, why not SymCrypt too. I would be happy about a PR.

[cpu]

We have botan as a builtin backend

Botan is a dev dependency only used for integration tests. It's not available as a backend for library consumers to provide cryptography implementations.

[juliusl]

I haven't given this deep thought yet, but my initial instinct is that we should consider following the rustls approach of making it possible for code external to the library to provide its own cryptography provider of choice and not bundling more options as built-in features.

That would be helpful, and then I would be able to just use the rustls-symcrypt provider

[djc]

Would you be able to submit a PR to add this abstraction, or fund the work to do so?

[juliusl]

Would you be able to submit a PR to add this abstraction, or fund the work to do so?

Sure, I don't mind taking a look at it