d5d8db7fa8
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. |
||
|---|---|---|
| .. | ||
| adapters | ||
| components | ||
| controllers | ||
| helpers | ||
| initializers | ||
| lib | ||
| mixins | ||
| models | ||
| pre-initializers | ||
| raw-views | ||
| routes | ||
| services | ||
| templates | ||
| widgets | ||
| mapping-router.js.es6 | ||