summaryrefslogtreecommitdiff
path: root/addons/web/static/src/js/views/basic/basic_controller.js
diff options
context:
space:
mode:
authorOlivier Dony <odo@odoo.com>2018-05-16 16:12:53 +0200
committerOlivier Dony <odo@odoo.com>2018-05-16 17:39:32 +0200
commit86ffb549bf80b054f8bb5131c52d3e7757accb29 (patch)
tree72910c822d8455de0cd3382428b88c079ee45ee0 /addons/web/static/src/js/views/basic/basic_controller.js
parent19fb650863f11172c8a6839fcc10919e9ca9977b (diff)
[FIX] base: log failed/successful logins with ip
We used to only log failed logins, and did not include the IP, which makes it much less useful for intrusion detections systems (e.g. fail2ban) For example, the following fail2ban filter definition should match a failed login (in /etc/fail2ban/filter.d/odoo-login.local): [Definition] failregex = ^ \d+ INFO \S+ \S+ Login failed for db:\S+ login:\S+ from <HOST> ignoreregex = This could be used with a jail definition to block the IP on HTTP(S). Here is what it could look like for blocking the IP for 15 minutes when 10 failed login attempts are detected from the same IP within 1 minute: [odoo-login] enabled = true port = http,https bantime = 900 ; 15 min ban maxretry = 10 ; if 10 attempts findtime = 60 ; within 1 min logpath = /var/log/odoo.log ; set the actual odoo log path here
Diffstat (limited to 'addons/web/static/src/js/views/basic/basic_controller.js')
0 files changed, 0 insertions, 0 deletions