discourse/app
Sam Saffron d5d8db7fa8 FEATURE: improve honeypot and challenge logic
This feature amends it so instead of using one challenge and honeypot
statically per site we have a rotating honeypot and challenge value which
changes every hour.

This means you must grab a fresh copy of honeypot and challenge value once
an hour or account registration will be rejected.

We also now cycle the value of the challenge when after successful account
registration forcing an extra call to hp.json between account registrations

Client has been made aware of these changes.

Additionally this contains a JavaScript workaround for:
https://bugs.chromium.org/p/chromium/issues/detail?id=987293

This is client side code that is specific to Chrome user agent and swaps
a PASSWORD type honeypot with a TEXT type honeypot.
2019-10-16 16:53:44 +11:00
..
assets FEATURE: improve honeypot and challenge logic 2019-10-16 16:53:44 +11:00
controllers FEATURE: improve honeypot and challenge logic 2019-10-16 16:53:44 +11:00
helpers SECURITY: mini profiler enabled incorrectly for admins 2019-10-09 12:49:22 +11:00
jobs FIX: Zeitwerk-related fixes for jobs. (#8187) 2019-10-14 13:03:22 +03:00
mailers FIX: during concurrent emails generation renderer should not be reused 2019-10-10 08:50:48 +11:00
models FIX: Add unique index to prevent duplicate slugs for categories 2019-10-15 19:44:50 +00:00
serializers FEATURE: Display created and last_used dates for API keys 2019-10-09 14:24:41 +01:00
services FIX: during concurrent emails generation renderer should not be reused 2019-10-10 08:50:48 +11:00
views Follow up fix to c71da3f, class was defined twice 2019-10-15 20:12:50 -04:00