[SERVER-22138] Investigate work involved to use native SSL implementations with ASIO Created: 11/Jan/16 Updated: 06/Dec/22 Resolved: 02/Mar/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Networking, Security |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Samantha Ritter (Inactive) | Assignee: | Backlog - Security Team |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Server Security
|
||||||||||||
| Sprint: | Platforms 10 (02/19/16) | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
The ASIO library has hard-coded dependencies on OpenSSL, but others have been able to port to other SSL implementations (BoringSSL) without a problem. We should investigate the work needed to port ASIO to SecureTransport/Common Crypto and SChannel/CNG. |