Valhalla Legends Archive

What is the max number of characters (letters) that battle.net allowes in a message?

230 truncated I think.

Quote from: Luxer on July 24, 2004, 09:23 AM
What is the max number of characters (letters) that battle.net allowes in a message?

If you're referring to a SID_CHATCOMMAND message, Battle.net truncates when text field is >0xe0 bytes (including null terminator).

Damn, was thinking the wrong thing. Was thinking charachter for usernames. Ooopppssss....  

Quote from: LordNevar on July 24, 2004, 10:36 AM
Damn, was thinking the wrong thing. Was thinking charachter for usernames. Ooopppssss....  

That's 16.

Since when? I thought it was 15....and a max password of 12

Quote from: ChR0NiC on July 24, 2004, 12:29 PM
Since when? I thought it was 15....and a max password of 12

Password length restriction is a client-side thing, correct?

Quote from: ChR0NiC on July 24, 2004, 12:29 PM
Since when? I thought it was 15....and a max password of 12

There can't be a limit on the password.

Quote from: UserLoser. on July 24, 2004, 01:07 PM

Quote from: ChR0NiC on July 24, 2004, 12:29 PM
Since when? I thought it was 15....and a max password of 12

There can't be a limit on the password.

Well, there could be problems if you create accounts with passwords longer than 12 characters using a emulation client.  If you try to logon to that account via a real client, you won't be able (without some sort of hack).  This is similar to the one discussion about the password having to be lower-case because the real clients do it.

Quote from: dxoigmn on July 24, 2004, 01:15 PM
Well, there could be problems if you create accounts with passwords longer than 12 characters using a emulation client.  If you try to logon to that account via a real client, you won't be able (without some sort of hack).  This is similar to the one discussion about the password having to be lower-case because the real clients do it.

So basically the client has certain restrictions only enforced by the client itself, and not the server. Wow BNET sure is bloody smart

PS: Yes I know how bloody smart they really are

Quote from: ChR0NiC on July 24, 2004, 01:18 PM

Quote from: dxoigmn on July 24, 2004, 01:15 PM
Well, there could be problems if you create accounts with passwords longer than 12 characters using a emulation client.  If you try to logon to that account via a real client, you won't be able (without some sort of hack).  This is similar to the one discussion about the password having to be lower-case because the real clients do it.

So basically the client has certain restrictions only enforced by the client itself, and not the server. Wow BNET sure is bloody smart

PS: Yes I know how bloody smart they really are

You try figuring out the length of a password after it's been hashed.

Techinically, the password can be virtually any length since its always hashed into a 160-bit digest.  But my question is how does the server verify the account via Telnet connection since the password is sent plaintext?

Quote from: Lenny on July 25, 2004, 03:17 AM
Techinically, the password can be virtually any length since its always hashed into a 160-bit digest.  But my question is how does the server verify the account via Telnet connection since the password is sent plaintext?

The server does the hash on the password itself and then compares it, obviously.

Quote from: Spht on July 24, 2004, 10:05 AM

Quote from: Luxer on July 24, 2004, 09:23 AM
What is the max number of characters (letters) that battle.net allowes in a message?

If you're referring to a SID_CHATCOMMAND message, Battle.net truncates when text field is >0xe0 bytes (including null terminator).

Ok, you could have just said 224.

Quote from: Maddox on July 25, 2004, 03:39 AM

Quote from: Spht on July 24, 2004, 10:05 AM

Quote from: Luxer on July 24, 2004, 09:23 AM
What is the max number of characters (letters) that battle.net allowes in a message?

If you're referring to a SID_CHATCOMMAND message, Battle.net truncates when text field is >0xe0 bytes (including null terminator).

Ok, you could have just said 224.

Easier to remember the hex code rather than a number which looks random.