[SERVER-22410] Define a generic SSL engine interface Created: 01/Feb/16 Updated: 06/Dec/22 Resolved: 22/Mar/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Networking |
| Affects Version/s: | 3.3.1 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Mira Carey | Assignee: | Backlog - Security Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Server Security
|
||||
| Participants: | |||||
| Description |
|
We need an interface that we can hide schannel and secure transport behind. This interface should provide block encryption/decryption as well as some level of configurability (access to system keychain seems the most useful) |
| Comments |
| Comment by Mark Benvenuto [ 22/Mar/18 ] |
|
asio::ssl::detail::engine already provides a good SSL abstract that integrates nicely with OpenSSL and ASIO. There is no need to create a new abstraction |