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.
Due to Google Chrome certification requirements we can expect
that in near future there will be no certificate authority
that will issue certifcates that have both server and client auth
purposes.
This change makes s2s listeners ignore cert purposes, and should
allow servers that have those new certificate to use it, to
authenticate new s2s connections.
This fixes issue #4392
Notice:
- installers use OTP 27.3.4.1, the latest available right now
- containers use OTP 27.3.4, because container for 27.3.4.1 was not published,
see https://hub.docker.com/_/erlang
This fixes the problem when stopping the module with multiple vhosts:
unsubscribing from a local pubsub requires mod_pubsub in that vhost running,
but ejabberd stops mod_pubsub from a vhost before stopping mod_antispam
in other vhost.
When ejabberd is being stopped
and some module calls ejabberd_logger:get_log_path(),
application:load/1 crashes with error:
** Reason for termination ==
** {terminating,
[{application_controller,call,2,
[{file,"application_controller.erl"},{line,511}]},
{application,load1,2,[{file,"application.erl"},{line,274}]},
{ejabberd_config,env_binary_to_list,2,
[{file,"/home/git/ejabberd/src/ejabberd_config.erl"},
{line,343}]},
{ejabberd_logger,get_log_path,0,
[{file,"/home/git/ejabberd/src/ejabberd_logger.erl"},
{line,55}]},
The option 'default_host' for ejabberd_http was added years ago
in commit 7d623d5. However it was problematic and the usage was
removed in commit 83c291c. It's time to remove its last forgotten bits.
