```
>>    but fixing up later on is more "expensive" than just not catching some quite rare malicious attempts.
> not following. Thought the filters for the rare attempts where what you're asking to fix later. Not sure what the expense is either.
```

;-) yes -- we want to catch malicious attempts.  but more importantly we would like to avoid catching "nonmalicious" normal activities.  If a failregex which triggers under normal use-cases becomes part of a release, and then adopted by stable releases of Linux distributions, it would become tedious (thus "expensive") to fix them all up in there.  Thus I would prefer to not catch some malicious attempts to help avoiding banning normal users.

I will merge it since it is outstanding stuff -- thanks a lot!  But I will follow up with a commit to disable this particular one "hash is not" since I am still not sure about it:  I understand that it is easy to trigger it from a test script, but I do not yet fully understand why in my case it gets triggered by normal use of zotero.  On a server with many users such messages might be even more common I bet.