Wanjohi fc825f5219 fix(auth): stop a caller working through the user code space ...

A user code is eight characters from a twenty-five character alphabet,
which is a large space but a fixed one, and the endpoint that checked
them had no opinion about how often you asked. That is the guessing
attack RFC 8628 section 5.2 asks implementations to limit, and nothing
here did.

Wrong codes are now counted per caller address over a rolling window,
and the endpoint stops answering once the budget is gone. Getting a code
right is not charged for, so somebody who mistypes once and then succeeds
is not walking towards a lockout. A caller whose address cannot be
established shares one bucket with every other such caller, which makes
stripping the headers that say where you are buy a smaller budget rather
than an unlimited one.

The counter lives in the general-purpose store and is approximate. The
number that decides this is whether somebody is working through the code
space, and a handful either way does not change that answer.

2026-09-05 09:54:59 +03:00

..

auth

fix(auth): stop a caller working through the user code space

2026-09-05 09:54:59 +03:00

core

fix(auth): make a device sign-in an answer somebody gave

2026-09-05 09:40:03 +03:00