diff options
| author | Jonas Schäfer <jonas@wielicki.name> | 2022-04-02 11:15:33 +0200 |
|---|---|---|
| committer | Jonas Schäfer <jonas@wielicki.name> | 2022-04-02 11:15:33 +0200 |
| commit | 9f7c3b9ba6c2fde4431cd6f3a12072518b478d69 (patch) | |
| tree | 32e0b232600b224369ead1e7c62194b19d549cc0 /core | |
| parent | 38346dd6f1dcd963e17722bf175445465d7683f4 (diff) | |
| download | prosody-9f7c3b9ba6c2fde4431cd6f3a12072518b478d69.tar.gz prosody-9f7c3b9ba6c2fde4431cd6f3a12072518b478d69.zip | |
net: refactor sslconfig to not depend on LuaSec
This now requires that the network backend exposes a tls_builder
function, which essentially wraps the former util.sslconfig.new()
function, passing a factory to create the eventual SSL context.
That allows a net.server backend to pick whatever it likes as SSL
context factory, as long as it understands the config table passed by
the SSL config builder. Heck, a backend could even mock and replace the
entire SSL config builder API.
Diffstat (limited to 'core')
| -rw-r--r-- | core/certmanager.lua | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/core/certmanager.lua b/core/certmanager.lua index 6013c633..7958e8a9 100644 --- a/core/certmanager.lua +++ b/core/certmanager.lua @@ -10,7 +10,7 @@ local ssl = require "ssl"; local configmanager = require "core.configmanager"; local log = require "util.logger".init("certmanager"); local ssl_newcontext = ssl.newcontext; -local new_config = require"util.sslconfig".new; +local new_config = require"net.server".tls_builder; local stat = require "lfs".attributes; local x509 = require "util.x509"; |