- Partially rewritten state resolution
- Support for Hydra rooms
- Use double colon for separating a matrix server from a room ID in JID
with Hydra rooms
- Partially rewritten mod_matrix_gw_s2s
- Add notary_servers option
Updates this GitHub Action that's used to execute XMPP-based interop tests from v1.5.0 to v1.6.0.
In this update, 524 new tests were added (more than doubling the amount of tests that previously existed).
For example:
hosts:
- localhost
- locälhost3
- xn--loclhost4-x2a
all them are converted to utf8:
ejabberd_option:hosts().
[<<"localhost">>,
<<"locälhost3"/utf8>>,
<<"locälhost4"/utf8>>]
and if that path is too long, then try HOME directory,
if that's too long too, throw error explaining the problem.
By the way, cutting the base64 string to 107 is a bad idea,
as it encodes the final path, which would get lost and crash.
The Erlang containers from versions 20-23 use Debian Buster,
and require the debian repositories to install some development libraries.
The Debian Buster repositories are no longer available,
which means that we can no longer perform any test with Erlang 20-23.
Make sure Linux-PAM doesn't attempt to include logind support. This
avoids a build failure in case the host system has systemd's
development headers installed.
This is important when running the ban_account command and mod_auth_fast
is enabled, as the client may store auth tokens that bypass
the banning stored in private storage and enforced by ejabberd_auth.
Previous version was only correct when data to process
was sorted, which was not always the case.
This add common implementation of lists:uniq in misc that works
also on <R25, and switches get_users to use it.
This option allows disabling some auth mechanisms
to be offered in SASL1 features. This makes adding
new password types easier, by ensuring that new
password use will be offered only to clients that
have new type stored (SASL2 clients that send us
user info before features need to be sent), but
not to clients where we don't know if they have
new passwords.
