- Oct 28, 2024
-
-
Badlop authored
-
Badlop authored
-
Paweł Chmielowski authored
-
Badlop authored
-
Badlop authored
-
Badlop authored
-
Badlop authored
-
Badlop authored
-
Badlop authored
-
Badlop authored
-
Badlop authored
-
Badlop authored
-
Badlop authored
See explanations following the comment https://github.com/processone/ejabberd/pull/4285#issuecomment-2397047355 This partially reverts commit 94c2a115.
-
Badlop authored
-
Badlop authored
New check_register_user hook in ejabberd_auth.erl to allow blocking account registration when a tombstone exists. Modified room_destroyed hook in mod_muc_room.erl Until now the hook passed as arguments: LServer, Room, Host. Now it passes: LServer, Room, Host, Persistent That new Persistent argument passes the room persistent option, required by mod_tombstones because only persistent rooms should generate a tombstone, temporary ones should not. And the persistent option should not be completely overwritten, as we must still known its real value even when room is being destroyed. mod_tombstones is available in experimental mode in ejabberd-contrib git. Initial feature request: #2546
-
Paweł Chmielowski authored
-
Paweł Chmielowski authored
-
Paweł Chmielowski authored
- Oct 21, 2024
- Oct 15, 2024
-
-
Holger Weiss authored
These days, TURN authentication is usually performed using ephemeral credentials handed out by mod_stun_disco. In that case, the TURN realm is irrelevant. Therefore, omit the misleading log message that warned about a missing realm configuration. (Commit 6eb2f072 reduced the log level of that message already.)
-
- Oct 11, 2024
-
-
Badlop authored
-
Badlop authored
-
Badlop authored
-
dependabot[bot] authored
Bumps [dialyxir](https://github.com/jeremyjh/dialyxir) from 1.4.3 to 1.4.4. - [Release notes](https://github.com/jeremyjh/dialyxir/releases) - [Changelog](https://github.com/jeremyjh/dialyxir/blob/master/CHANGELOG.md) - [Commits](https://github.com/jeremyjh/dialyxir/compare/1.4.3...1.4.4 ) --- updated-dependencies: - dependency-name: dialyxir dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by:
dependabot[bot] <support@github.com>
-
Badlop authored
-
badlop authored
CI: Add XMPP Interop tests
-
- Oct 09, 2024
-
-
Holger Weiss authored
-
- Oct 08, 2024
-
-
Holger Weiss authored
This fixes announcing SASL2 over non-TLS connections if 'allow_unencrypted_sasl2' is configured.
-
- Oct 01, 2024
- Sep 29, 2024
-
-
Holger Weiss authored
XEP-0388 says: "SASL2 MUST only be used by Clients or offered by Servers after TLS negotiation". Therefore, we reject SASL2 negotiations over unencrypted transports by default. However, TLS might be terminated outside of ejabberd. Add the 'allow_unencrypted_sasl2' option to support this use case.
-
- Sep 28, 2024
-
-
Holger Weiss authored
If the plugin handling a node creation request isn't enabled, fall back to applying the default plugin (currently node_flat) options.
-
Holger Weiss authored
Ignore node plugin defaults if the plugin handling the request isn't enabled, rather than ignoring 'default_node_config' options and applying plugin defaults in that case.
-
Holger Weiss authored
Use any option specified via 'default_node_config' by default, and take the remaining defaults from the node plugin handling the request. This is the documented behavior. Before this change, the code applied the plugin defaults only if no 'default_node_config' existed at all. And even this logic didn't work as intended, since 'default_node_config' yielded an empty list in case it wasn't configured, which resulted in plugin defaults never being applied.
-
Holger Weiss authored
Don't merge 'default_node_config' settings with the default options of the first configured node plugin. Otherwise, the latter might later override those of the plugin that should handle a node creation request. For example, the following configuration would lead to the 'flat' options being used by default for 'pep' nodes as well: mod_pubsub: plugins: - flat - pep
-
- Sep 27, 2024
-
-
Guus der Kinderen authored
Run the XMPP Interop tests on only one build of the CI-matrix. This prevents redundant testing, as well as logs overwriting each-other.
-