[SERVER-83695] Customer facing SSL certificate errors PyMongo v6.0: "Unsafe Legacy Renegotiation" Created: 28/Nov/23 Updated: 03/Feb/24 Resolved: 18/Dec/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jib Adegunloye | Assignee: | Gabriel Marks |
| 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
|
||||||||
| Operating System: | ALL | ||||||||
| Sprint: | Security 2023-12-11, Security 2023-12-25 | ||||||||
| Participants: | |||||||||
| Description |
|
Linked Ticket: HELP-51899 Customer reports now being unable to connect to Mongo Server v6.0. Further troubleshooting showed:
Which should mean the server is attempting renegotiation. However, PyOpenSSL exposed the `OP_NO_RENEGOTATION` flag since 22.0.0 and the customer is on 23.2.0. We're thinking of supporting renegotation through pymongo by adding the OP_LEGACY_SERVER_CONNECT flag.
This end result has led to two main questions:
|
| Comments |
| Comment by Jib Adegunloye [ 28/Nov/23 ] |