Software /
code /
prosody
Annotate
spec/scansion/version.scs @ 12481:2ee27587fec7
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.
author | Jonas Schäfer <jonas@wielicki.name> |
---|---|
date | Sat, 02 Apr 2022 11:15:33 +0200 |
parent | 10729:dbce2b94a7eb |
rev | line source |
---|---|
10729 | 1 # XEP-0092: Software Version / mod_version |
2 | |
3 [Client] Romeo | |
4 password: password | |
5 jid: romeo@localhost/dfaZpuxV | |
6 | |
7 ----- | |
8 | |
9 Romeo connects | |
10 | |
11 Romeo sends: | |
12 <iq id='lx2' to='localhost' type='get'> | |
13 <query xmlns='jabber:iq:version'/> | |
14 </iq> | |
15 | |
16 # Version string would vary so we can't do an exact match atm | |
17 # Inclusion of <os/> is disabled in the config, it should be absent | |
18 Romeo receives: | |
19 <iq id='lx2' from='localhost' type='result'> | |
20 <query xmlns='jabber:iq:version' scansion:strict='true'> | |
21 <name>Prosody</name> | |
22 <version scansion:strict='false'/> | |
23 </query> | |
24 </iq> | |
25 | |
26 | |
27 Romeo disconnects |