| Age | Commit message (Collapse) | Author |
|---|
|
Add a new listener on port 5223 for the TLS-enabled ejabberd_c2s, which combined with proper SRV records allows passing the XEP-0368 compliance test.
|
|
|
|
|
|
|
|
The stun application now supports RFC 6156: TURN Extension for IPv6, and
therefore needs separate IPv4 and IPv6 relay addresses.
|
|
The stun application now allows IPv6 clients to perform STUN requests
and to allocate TURN relays.
|
|
More discussion about this can be found in pull request 3255
|
|
Enable STUN/TURN support by default
|
|
Add the 'mod_stun_disco' module, which allows XMPP clients to discover
STUN/TURN services and to obtain temporary credentials for using them as
per XEP-0215: External Service Discovery. The temporary credentials
handed out to clients have the format described in:
https://tools.ietf.org/html/draft-uberti-behave-turn-rest-00
Also add the new module to the example configuration file.
Closes #2947.
|
|
Build ejabberd with STUN/TURN support by default, and add a STUN/TURN
listener to the example configuration file.
|
|
This change requires Erlang/OTP-21.0 or higher.
The commit also deprecates the following options:
- log_rotate_date
- log_rate_limit
Furthermore, these options have no effect. The logger now fully
relies on log_rotate_size, that cannot be 0 anymore.
The loglevel option now accepts levels in literal formats.
Those are: none, emergency, alert, critical, error, warning, notice, info, debug.
Old integer values (0-5) are still supported and automatically converted
into literal format.
|
|
|
|
Rely on ACME configuration instead
|
|
|
|
|
|
|
|
The 'register' access rule isn't referenced from the 'mod_register'
options, so modifying it would have no effect.
|
|
Those are: captcha, register, web_admin, http_bind and xmlrpc
The option `request_handlers` should be used instead, e.g.:
listen:
...
-
module: ejabberd_http
request_handlers:
"/admin": ejabberd_web_admin
"/bosh": mod_bosh
"/captcha": ejabberd_captcha
"/register": mod_register_web
"/": ejabberd_xmlrpc
|
|
The purpose is two-fold:
- To simplify the example config.
- To avoid old TLS configuration to be persistent across
server updates: this might bring security problems, because
what's considered "modern" now might be insecure in the future.
|
|
This doesn't work reliably and takes a lot of effort to change it back
|
|
|
|
|
|
|
|
|
|
|
|
|
|
...instead of "comment out", as many seem to misunderstand what and why should be or not be commented out
|
|
|
|
|
|
Specify a larger 'max_stanza_size' limit for c2s connections in the
default configuration in order to reduce the risk of this limit being
hit by legitimate traffic (such as avatar uploads).
|
|
Specify a 'max_stanza_size' limit for incoming s2s connections in the
example configuration, but use a relatively large value in order to
minimize the risk of this limit being hit by legitimate traffic.
|
|
|
|
|
|
Are these important for a new admin?
|
|
|
|
|
|
...in enable OMEMO
|
|
After some discussion with the community it was decided to
clean the configuration file from excessive comments and
explicitly configured default values. Also, mod_mam and
mod_http_upload have been added.
The rationale for this is to have a clean and not bloated
configuration file which doesn't scare away newcomers and
which has all features from the Compliance Suite 2018 (XEP-0387)
enabled by default.
For further configuration an admin is encouraged to read the
documentation at https://docs.ejabberd.im/admin/configuration
|
|
|
|
Depend on #2425
|
|
I only found it in the docs after setting up per module db_
|
|
|
|
(to ease parameters comparison)
|
|
|
|
|
|
|
|
default value to true (#2239)
|
|
|
|
Even if no suitable C graphics libraries are detected
at compile time, the package is still usable because it
provides `eimp:get_type/1` which is used by mod_avatar.
|
|
These were missed in https://github.com/processone/ejabberd/commit/c26b56679e06ef8b88734030de11c6b885f9bb78#diff-19e0c10699732f76181f70cfbec95d38 I guess.
|
