gamer147 a786599416 fix(battle-node): clarify NodeCrypto.GenerateKey contract + add fixed-vector regression test ...

Replace inaccurate GenerateKey docstring (it claimed to port Cryptographer.generateKeyString
directly but the input shape differs: server uses one hex digit per call, client uses
Random.Next(0,65535) per call). New doc is honest about the difference and explains why
it's safe. Add EncryptForNode_FixedVector_ProducesStableOutput: a pinned AES-CBC vector
that catches encoding/IV/padding regressions that would slip past the roundtrip test.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

2026-05-31 21:31:22 -04:00

3.2 KiB

Raw Blame History

View Raw