Provider Ciphers and Rand

[mamckee]

This PR adds cipher and RNG implementations to the Symcrypt Provider. The source files for the SymCrypt engine have all been prefixed with "e_" to avoid confusion with common source files.

The implementation for GCM and CCM has been refactored into common code shared between the provider and engine.

The following ciphers have been added:

• AES-128-CBC
• AES-192-CBC
• AES-256-CBC
• AES-128-CFB (128-bit shift)
• AES-192-CFB (128-bit shift)
• AES-256-CFB (128-bit shift)
• AES-128-CFB (8-bit shift)
• AES-192-CFB (8-bit shift)
• AES-256-CFB (8-bit shift)
• AES-128-ECB
• AES-192-ECB
• AES-256-ECB
• AES-128-GCM
• AES-192-GCM
• AES-256-GCM
• AES-128-CCM
• AES-192-CCM
• AES-256-CCM
• AES-128-XTS (disabled for now)
• AES-256-XTS (disabled for now)

[samuel-lee-msft]

LIBRARY DESTINATION "${CMAKE_INSTALL_LIBDIR}/ossl-modules"

Probably a good plan to use a new variable like OPENSSL_PROVIDERS, like: https://github.com/microsoft/SymCrypt-OpenSSL/pull/58/files#diff-f79d526d98446e8093575181d6dec16feb7cf2cd4c3882cc9bee910fa54fd5ce

---

Refers to: SymCryptProvider/CMakeLists.txt:50 in d5c545f. [](commit_id = d5c545f7c790636e5c7a99a21900a7dbbe004214, deletion_comment = False)

[mamckee]

@samuel-lee-msft, I added CFB to this PR. SymCrypt only supports 128- and 8-bit shifts, but OpenSSL also supports 1-bit shifts registered as separate algorithms. Is this something we need to support in the SymCrypt provider or can we fall back to the default provider?

---

In reply to: 1500728890

[samuel-lee-msft]

Fine to fallback here - but when we update the README it should be clear.

---

In reply to: 1500728890