http://hg.omfa.de/prosody-hg/ en-us prosody-hg: net/tls_luasec.lua history net/tls_luasec.lua revision history util.sslconfig: Support DH parameters as literal string http://hg.omfa.de/prosody-hg/log/61da4491eebc/net/tls_luasec.lua
Simplifies shipping well-known DH parameters in the config]]> Kim Alvefur <zash@zash.se> Fri, 12 Jul 2024 15:21:08 +0200 net.tls_luasec: Expose method for loading a certificate http://hg.omfa.de/prosody-hg/log/58e793288d9c/net/tls_luasec.lua
Further isolates LuaSec from Prosody core, with the ultimate goal of
allowing LuaSec to be replaced more easily.]]> Kim Alvefur <zash@zash.se> Sat, 27 May 2023 15:40:49 +0200 net.certmanager: Move LuaSec feature detection to net.tls_luasec http://hg.omfa.de/prosody-hg/log/749376d75b40/net/tls_luasec.lua
Further isolates LuaSec from Prosody core, with the ultimate goal of
allowing LuaSec to be replaced more easily.]]> Kim Alvefur <zash@zash.se> Sat, 27 May 2023 15:39:26 +0200 net.tls_luasec: Harden dependency on LuaSec http://hg.omfa.de/prosody-hg/log/ee93df086926/net/tls_luasec.lua
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.]]> Kim Alvefur <zash@zash.se> Wed, 27 Apr 2022 21:34:35 +0200 net: isolate LuaSec-specifics http://hg.omfa.de/prosody-hg/log/7e9ebdc75ce4/net/tls_luasec.lua
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.]]> Jonas Schäfer <jonas@wielicki.name> Wed, 27 Apr 2022 17:44:14 +0200