Mercurial > prosody-modules
view mod_auth_external_insecure/examples/bash/prosody-auth-example.sh @ 5787:e79f9dec35c0
mod_c2s_conn_throttle: Reduce log level from error->info
Our general policy is that "error" should never be triggerable by remote
entities, and that it is always about something that requires admin
intervention. This satisfies neither condition.
The "warn" level can be used for unexpected events/behaviour triggered by
remote entities, and this could qualify. However I don't think failed auth
attempts are unexpected enough.
I selected "info" because it is what is also used for other notable session
lifecycle events.
author | Matthew Wild <mwild1@gmail.com> |
---|---|
date | Thu, 07 Dec 2023 15:46:50 +0000 |
parents | f84ede3e9e3b |
children |
line wrap: on
line source
#!/bin/bash IFS=":" AUTH_OK=1 AUTH_FAILED=0 LOGFILE="/var/log/prosody/auth.log" USELOG=false while read ACTION USER HOST PASS ; do [ $USELOG == true ] && { echo "Date: $(date) Action: $ACTION User: $USER Host: $HOST Pass: $PASS" >> $LOGFILE; } case $ACTION in "auth") if [ $USER == "someone" ] ; then echo $AUTH_OK else echo $AUTH_FAILED fi ;; *) echo $AUTH_FAILED ;; esac done