Memory Corruption in EQEmuAuthCrypto

[daerath]

Description: Output from EQEmuAuthCrypto's Encrypt method varies if a debugger is attached.

Test: Attach debugger to LoginServer.exe and step through processing of the client's OP_Login packet. After a successful database lookup, the login_replyblock_struct is passed into the Encrypt method. If a debugger is not attached, the output is correct. If a debugger is attached, the first 72 bytes are correct, but the final 8 byte block is not.

Not a crash bug.

[daerath]

Follow up on this one. I did confirm that this is a real bug by writing a fully managed code version. I took the output from EQEmuAuthCrypto's Encrypt method (with a debugger attached) and tried to decrypt it using the same algorithm, key, iv, and padding mode used by the EQEmuAuthCrypto DLL and it failed every time.

The output produced by EQEmuAuthCrypto (without a debugger attached) decrypts perfectly every time.

Still not a crash bug, so it'll probably never get fixed, but I wanted to follow up on this anyway.