Solved.

[Dro]

Solved.

http://forum.valhallalegends.com/phpbbs/index.php?topic=11267.0

[UserLoser.]

BYTE[20] - M1
BYTE[32] - S
BYTE[32] - V

See this page for more info

[Dro]

Solved.

[MyndFyre]

BYTE[20] - M1
BYTE[32] - S
BYTE[32] - V

See this page for more info

What is M1, S, V?
What variables are those and how do they relate to the account password and such?

UserLoser pointed you to that page for a reason.  Battle.net uses the SRP (Secure Remote Password) exchange for user authentication, which includes account creation and password change.

M1 is a calculated hash of several components.  It's the client password proof, calculated via the following formula:
M1 = SHA1(SHA1(g) xor SHA1(N), SHA1(Username), s, A, B, K)
Note that SHA1 is that standard SHA-1 hashing function, not the "broken" implementation found in other Blizzard clients.
S is the "secret" value.  Essentially, both sides calculate it independently, with different values, and are supposed to come up with the same result.  This is how they know they have a valid exchange mechanism.  It is calculated for the client with the formula:
S = ((N + B - v) % N)^{(a + u * x)} % N
V is the password verifier, calculated with:
v = g^x % N

All of this information can be found on BnetDocs.  If you're using BNLS, it supports calculating the values for these messages.  See the BNLS Protocol Specification for more information.

Additionally, iago[vL] has documented the SRP key exchange used with Battle.net, and it should prove to be an invaluable reference.

Next time, please read information on the "see also" or "see for more information" pages that we link to instead of just asking for information found on those pages.  It will make us that much more inclined to help you.

[iago]

Additionally, iago[vL] has documented the SRP key exchange used with Battle.net, and it should prove to be an invaluable reference.

That'll give you everything you need to know including packet structures, formulas, and code samples (in Java, but easily ported to .net or C).

[Dro]

Solved.

[iago]

SID_AUTH_ACCOUNTCHANGE = BNCS packet 0x55 ?
SID_AUTH_ACCOUNTCHANGEPROOF = BNCS packet 0x56 ?

[C>0x55] SID_AUTH_ACCOUNTCHANGE
[S>0x55] SID_AUTH_ACCOUNTCHANGE
[C>0x56] SID_AUTH_ACCOUNTCHANGEPROOF
[S>0x56] SID_AUTH_ACCOUNTCHANGEPROOF

Yep.  Sorry, I forgot that Arta hasn't added that to BNetDocs yet.