New option to use and configure Prosody mod_firewall WIP (#97):
* new setting * new configuration screen for Peertube admins * include the mod_firewall module * load mod_firewall if enabled * sys admin can disable the firewall config editing by creating a special file on the disk * user documentation
This commit is contained in:
20
prosody-modules/mod_firewall/scripts/spam-blocklists.pfw
Normal file
20
prosody-modules/mod_firewall/scripts/spam-blocklists.pfw
Normal file
@ -0,0 +1,20 @@
|
||||
# This script depends on spam-blocking.pfw also being loaded
|
||||
# Any traffic that is not explicitly blocked or allowed by other
|
||||
# rules will be checked against the JabberSPAM server blocklist
|
||||
|
||||
%LIST blocklist: https://cdn.jsdelivr.net/gh/jabberspam/blacklist/blacklist.txt
|
||||
|
||||
::user/spam_handle_unknown_custom
|
||||
|
||||
CHECK LIST: blocklist contains $<@from|host>
|
||||
BOUNCE=policy-violation (Your server is blocked due to spam)
|
||||
|
||||
::user/spam_check_muc_invite_custom
|
||||
|
||||
# Check the server we received the invitation from
|
||||
CHECK LIST: blocklist contains $<@from|host>
|
||||
BOUNCE=policy-violation (Your server is blocked due to spam)
|
||||
|
||||
# Check the inviter's JID against the blocklist, too
|
||||
CHECK LIST: blocklist contains $<{http://jabber.org/protocol/muc#user}x/invite@from|host>
|
||||
BOUNCE=policy-violation (Your server is blocked due to spam)
|
Reference in New Issue
Block a user