Software /
code /
prosody
File
spec/scansion/tombstones.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 | 12116:efcf25ad5406 |
line wrap: on
line source
# Tombstones [Client] Romeo jid: romeo@localhost password: password [Client] Juliet jid: juliet-tombstones@localhost password: password --------- Romeo connects Juliet connects Juliet sends: <iq type="set" id="bye"> <query xmlns="jabber:iq:register"> <remove/> </query> </iq> # Scansion gets disconnected right after this with a stream error makes # scansion itself abort, so we preemptively disconnect to avoid that # Juliet receives: # <iq type="result" id="bye"/> Juliet disconnects Romeo sends: <presence type="probe" to="${Juliet's JID}"/> Romeo receives: <presence type="error" from="${Juliet's JID}"/> Romeo receives: <presence type="unsubscribed" from="${Juliet's JID}"/>