diff options
Diffstat (limited to 'releasenotes/notes/Fix-to-address-denylist-invalid-patterns-not-being-checked-ec1f1316ccc6cb1d.yaml')
| -rw-r--r-- | releasenotes/notes/Fix-to-address-denylist-invalid-patterns-not-being-checked-ec1f1316ccc6cb1d.yaml | 16 |
1 files changed, 16 insertions, 0 deletions
diff --git a/releasenotes/notes/Fix-to-address-denylist-invalid-patterns-not-being-checked-ec1f1316ccc6cb1d.yaml b/releasenotes/notes/Fix-to-address-denylist-invalid-patterns-not-being-checked-ec1f1316ccc6cb1d.yaml new file mode 100644 index 00000000..43a3ca94 --- /dev/null +++ b/releasenotes/notes/Fix-to-address-denylist-invalid-patterns-not-being-checked-ec1f1316ccc6cb1d.yaml @@ -0,0 +1,16 @@ +--- +fixes: + - | + Fixes `bug 1934252`_ which ignored invalid denylist patterns. The fix + entailed checking the pattern string via regular expression compiler and + testing for zero length. + + Previously you could create blacklist/denylist using string that cannot + be used either as a regex or as a zone name, for example: + patterns = ['', ``'#(*&^%$%$#@$']`` + + In addition, the server will return a 400 BadRequest response to an + invalid pattern. + + .. _Bug 1934252: https://bugs.launchpad.net/designate/+bug/1934252 + |