mirror of
https://github.com/diegosouzapw/OmniRoute.git
synced 2026-07-31 04:12:10 +03:00
57794cb8d8
* docs(security): add BAN_DETECTION.md — banned-keyword / account-ban detection (#5600) New docs/security/BAN_DETECTION.md documenting the previously-undocumented system: - the 8 built-in ACCOUNT_DEACTIVATED_SIGNALS + custom keywords are additive - detection flow (body substring match -> terminal `banned` state, skipped in account selection; `deactivated` on 401/403; autoDisableBannedAccounts) - scope: global (all providers); the signal strings target OAuth/subscription scrapers - custom keywords: add path, 200-char cap, hot-reload, and the false-positive warning (raw substring match -> prefer full ban sentences, not "quota"/"limit") - recovery: terminal states never auto-recover -> re-test / re-auth / re-enable Registered in security meta.json; cross-linked from RESILIENCE_GUIDE (terminal states). Docs-only. Closes #5600 * docs(security): clarify deactivated vs expired terminal-status split (#5600) The same ACCOUNT_DEACTIVATED signal surfaces as two different terminal statuses depending on the code path: chatCore.ts inline writes 'deactivated' (401/403 via classifyProviderError), while markAccountUnavailable() -> resolveTerminalConnectionStatus() writes 'expired'. Document both.
16 lines
257 B
JSON
16 lines
257 B
JSON
{
|
|
"title": "Security",
|
|
"pages": [
|
|
"GUARDRAILS",
|
|
"PUBLIC_CREDS",
|
|
"ERROR_SANITIZATION",
|
|
"ROUTE_GUARD_TIERS",
|
|
"BAN_DETECTION",
|
|
"STEALTH_GUIDE",
|
|
"EGRESS_POLICY",
|
|
"COMPLIANCE",
|
|
"SOCKET_DEV_FINDINGS",
|
|
"CLI_TOKEN"
|
|
]
|
|
}
|