Sam Sung 19af95006b Unattended logins answer a PIN from WOW_PIN or WOW_PIN_TOTP (#2386) ...

An unattended login (`WOW_USER` plus `WOW_PASS`) could not answer a PIN-protected account's keypad, so it waited forever.

Two variables now answer it. They go through the same path as the keypad's `PINEntered`, with the same prompt check and the same state report:
- `WOW_PIN`: the digits, as typed.
- `WOW_PIN_TOTP`: a base32 secret. Its RFC 6238 code (HMAC-SHA1, 30 s step, 6 digits) is the PIN, the scheme vmangos verifies (`AuthSocket.cpp:1274`). The code is derived at each prompt, re-dials included.

Setting both is refused, and neither value is ever logged. The variables are documented under "Running it unattended".

Tests: the RFC 6238 vectors, a leading-zero code, each variable answering the prompt, both set refused, and fresh codes on a mocked clock. A live fixed-PIN login against vmangos passed.

Fixes #2371

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-25 09:46:06 +07:00

..

examples

PIN-protected accounts can log in, as in 1.12.1 (#2367)

2026-10-25 03:03:35 +07:00

src

Unattended logins answer a PIN from WOW_PIN or WOW_PIN_TOTP (#2386)

2026-10-25 09:46:06 +07:00

tests

The login dialog walks every logon state, as 1.12.1's does (#2369)

2026-10-25 04:50:49 +07:00

Cargo.toml

Console commands and CVars follow 1.12.1; Lua's date and time are local (#2257)

2026-10-22 23:28:59 +07:00