| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | net.certmanager: Move LuaSec feature detection to net.tls_luasec | Kim Alvefur | 2023-05-27 | 1 | -0/+24 |
| | | | | | | Further isolates LuaSec from Prosody core, with the ultimate goal of allowing LuaSec to be replaced more easily. | ||||
| * | net.tls_luasec: Harden dependency on LuaSec | Kim Alvefur | 2022-04-27 | 1 | -3/+2 |
| | | | | | | | We at some point decided that it was okay to have a hard dependency the TLS library. Especially here since this module is meant to contain all LuaSec specifics. | ||||
| * | net: isolate LuaSec-specifics | Jonas Schäfer | 2022-04-27 | 1 | -0/+90 |
| For this, various accessor functions are now provided directly on the sockets, which reach down into the LuaSec implementation to obtain the information. While this may seem of little gain at first, it hides the implementation detail of the LuaSec+LuaSocket combination that the actual socket and the TLS layer are separate objects. The net gain here is that an alternative implementation does not have to emulate that specific implementation detail and "only" has to expose LuaSec-compatible data structures on the new functions. | |||||
 |
index : prosody.git | |
| unofficial mirror of the prosody mercurial project |
| aboutsummaryrefslogtreecommitdiffstats |