|
2024-11-12
| ||
| 00:59 | • Ticket [d52f608f92] Add server support to OFTLSStream status still Open with 3 other changes artifact: 238d74ebf5 user: js | |
|
2024-05-22
| ||
| 20:13 | • Ticket [d52f608f92]: 1 change artifact: f1fd8279f9 user: js | |
| 00:15 | • Ticket [d52f608f92]: 4 changes artifact: 40f76bb18b user: js | |
|
2021-11-21
| ||
| 09:59 | • New ticket [d52f608f92]. artifact: f102eac2a8 user: js | |
| Ticket UUID: | d52f608f92f1a54ff9989a2f98e9bcb4acf34070 | |||
| Title: | Add server support to OFTLSStream | |||
| Status: | Open | Type: | Feature Request | |
| Severity: | Important | Priority: | Medium | |
| Subsystem: | Resolution: | Open | ||
| Last Modified: | 2024-11-12 00:59:55 | |||
| Version Found In: | Milestone: | 1.3 | ||
| User Comments: | ||||
|
js added on 2021-11-21 09:59:27:
OFTLSStream currently only has client support. While adding server support itself is not hard, finding an abstract enough API is: Different TLS libraries take certificates in a different form, some from files, some from a system cert store. There needs to be a way flexible enough that works with all of them. | ||||