The gym checks whether a hidden secret leaked by scanning each HTTP response for every secret value (plus a few encodings of it). That is fine for one small app, but in a big world with many secrets it is one substring search per secret per response, which gets slow.
When we scale up, replace the per-secret loop with a single multi-pattern matcher (Aho-Corasick).
Not urgent. Only matters once a world has many secrets. Comes from the leak detection added in PR #259; relevant to the enterprise direction (#212).
The gym checks whether a hidden secret leaked by scanning each HTTP response for every secret value (plus a few encodings of it). That is fine for one small app, but in a big world with many secrets it is one substring search per secret per response, which gets slow.
When we scale up, replace the per-secret loop with a single multi-pattern matcher (Aho-Corasick).
Not urgent. Only matters once a world has many secrets. Comes from the leak detection added in PR #259; relevant to the enterprise direction (#212).