Thomas Waldmann 4c49ef5613 add BAD_HOSTS setting for nasty clients ...

having one who updates every 5s with a invalid password.
this locks the database (due to it increasing auth fail count and msg)
all the time, so i can't even delete that host from django admin.

also: Response now get a status parameter, defaulting to 200.

2019-04-15 18:57:54 +02:00

..

accounts

git mv nsupdate src/

2019-04-04 01:04:16 +02:00

api

add BAD_HOSTS setting for nasty clients

2019-04-15 18:57:54 +02:00

locale

add spanish translation (es), incomplete still, 85%

2019-04-14 17:14:02 +02:00

login

git mv nsupdate src/

2019-04-04 01:04:16 +02:00

main

fix crash / add logging for reverse lookup on invalid ip address string

2019-04-14 22:12:20 +02:00

management

django-admin faults: show/reset api auth faults counter

2019-04-09 12:08:00 +02:00

settings

add BAD_HOSTS setting for nasty clients

2019-04-15 18:57:54 +02:00

static

git mv nsupdate src/

2019-04-04 01:04:16 +02:00

templates

use "load static", fixes #403

2019-04-08 21:16:00 +02:00

utils

git mv nsupdate src/

2019-04-04 01:04:16 +02:00

__init__.py

fix setuptools_scm usage related crash, fixes #423

2019-04-09 22:26:07 +02:00

context_processors.py

git mv nsupdate src/

2019-04-04 01:04:16 +02:00

urls.py

git mv nsupdate src/

2019-04-04 01:04:16 +02:00

wsgi.py

git mv nsupdate src/

2019-04-04 01:04:16 +02:00