Page MenuHomePhabricator

Replace old rate limiting in password login flow with "SystemAction" rate limiting
ClosedPublic

Authored by epriestley on Jul 19 2019, 5:21 PM.
Tags
None
Referenced Files
Unknown Object (File)
Tue, Jan 21, 9:31 AM
Unknown Object (File)
Fri, Jan 17, 10:21 PM
Unknown Object (File)
Tue, Dec 24, 8:41 AM
Unknown Object (File)
Dec 21 2024, 5:50 PM
Unknown Object (File)
Dec 20 2024, 4:57 PM
Unknown Object (File)
Dec 17 2024, 6:03 AM
Unknown Object (File)
Dec 15 2024, 8:46 AM
Unknown Object (File)
Dec 13 2024, 8:54 AM
Subscribers
None

Details

Summary

Depends on D20667. Ref T13343. Password auth currently uses an older rate limiting mechanism, upgrade it to the modern "SystemAction" mechanism.

This mostly just improves consistency, although there are some tangential/theoretical benefits:

  • it's not obvious that making the user log GC very quickly could disable rate limiting;
  • if we let you configure action limits in the future, which we might, this would become configurable for free.
Test Plan
  • With CAPTCHAs off, made a bunch of invalid login attempts. Got rate limited.
  • With CAPTCHAs on, made a bunch of invalid login attempts. Got downgraded to CAPTCHAs after a few.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

src/applications/auth/provider/PhabricatorPasswordAuthProvider.php
258–260

These limits have changed slightly: captcha from "5 per 15 minutes" to "10 per hour", and logins from "32 per 15 minutes" to "100 per hour".

This revision is now accepted and ready to land.Jul 19 2019, 9:43 PM