Mercurial > prosody-modules
annotate mod_log_sasl_mech/mod_log_sasl_mech.lua @ 4515:2e33eeafe962
mod_muc_markers: Prevent any markers from reaching the archive, even if untracked
Original intention was to leave alone things that this module isn't
handling. However markers in archives are just problematic without
more advanced logic about what is markable and what is not. It also
requires a more advanced query in mod_muc_rai to determine the latest
markable message instead of the latest archived message.
I'd rather keep the "is archivable" and "is markable" definition the
same for simplicity. I don't want to introduce yet another set of rules
for no reason.
No markers in MAM.
author | Matthew Wild <mwild1@gmail.com> |
---|---|
date | Mon, 22 Mar 2021 15:55:02 +0000 |
parents | 4baaa5a66a5a |
children | 5ff8022466ab |
rev | line source |
---|---|
1292
2d061333d0c2
mod_log_sasl_mech: Logs authentication mechanism used
Kim Alvefur <zash@zash.se>
parents:
diff
changeset
|
1 |
2d061333d0c2
mod_log_sasl_mech: Logs authentication mechanism used
Kim Alvefur <zash@zash.se>
parents:
diff
changeset
|
2 module:hook("authentication-success", function (event) |
1393
4baaa5a66a5a
mod_log_sasl_mech: Log SASL mechanism attached to session
Kim Alvefur <zash@zash.se>
parents:
1292
diff
changeset
|
3 local session = event.session; |
4baaa5a66a5a
mod_log_sasl_mech: Log SASL mechanism attached to session
Kim Alvefur <zash@zash.se>
parents:
1292
diff
changeset
|
4 local sasl_handler = session.sasl_handler; |
4baaa5a66a5a
mod_log_sasl_mech: Log SASL mechanism attached to session
Kim Alvefur <zash@zash.se>
parents:
1292
diff
changeset
|
5 session.log("info", "Authenticated with %s", sasl_handler and sasl_handler.selected or "legacy auth"); |
1292
2d061333d0c2
mod_log_sasl_mech: Logs authentication mechanism used
Kim Alvefur <zash@zash.se>
parents:
diff
changeset
|
6 end); |