Valhalla Legends Archive

I was fooling around testing the war3 java stuff and I found out that the 2nd dword (version hash) in SID_AUTH_CHECK can be set to anything. This also is true for the executable information. If you're thinking you might get ipbanned or get sent an invalid version message in the future, you won't. The reason is that Mac users don't send this information either. Blizzard couldn't implement as complete a CheckRevision for them, due to the lack of the Windows API on the Mac, so they simply made those fields optional. If TestBNCS is still being updated, it should probably be made to ignore those fields too if it doesn't already.

This is nice to know if you're doing work on other platforms other than Windows because you don't need to hardcode those values in anymore.

So does that mean by using PMAC or XMAC instead of IX86, you wouldn't need to actually hash war3...?

It means that you don't need to put anything there.

Quote from: PiaNKA on August 17, 2004, 07:26 AM
So does that mean by using PMAC or XMAC instead of IX86, you wouldn't need to actually hash war3...?

I think you're using the word "hash" wrong.  Hash is a process of compression data to a smaller representation.  In this case, he means just the version hash, which is a small part of the login.

Quote from: iago on August 17, 2004, 11:10 AM

Quote from: PiaNKA on August 17, 2004, 07:26 AM
So does that mean by using PMAC or XMAC instead of IX86, you wouldn't need to actually hash war3...?

I think you're using the word "hash" wrong.  Hash is a process of compression data to a smaller representation.  In this case, he means just the version hash, which is a small part of the login.

Right but if it can be anything, it can be always 0, right?  Which would make it so you wouldn't need to do a version hash at all...

Quote from: PiaNKA on August 17, 2004, 12:05 PM

Quote from: iago on August 17, 2004, 11:10 AM

Quote from: PiaNKA on August 17, 2004, 07:26 AM
So does that mean by using PMAC or XMAC instead of IX86, you wouldn't need to actually hash war3...?

I think you're using the word "hash" wrong.  Hash is a process of compression data to a smaller representation.  In this case, he means just the version hash, which is a small part of the login.

Right but if it can be anything, it can be always 0, right?  Which would make it so you wouldn't need to do a version hash at all...

The "version hash" is just a value returned by the win32 version of CheckRevision. And yes, it can always be 0.

Quote from: Maddox on August 17, 2004, 03:51 PM
The "version hash" is just a value returned by the win32 version of CheckRevision. And yes, it can always be 0.

Oh, so it's not anything more complicated than a Win32 API call?  That would be interesting if Mac's couldn't handle hashing war3 and you could simply bypass all of it by saying you're on a different platform.  Though that would defeat the entire purpose of hashing and would leak tons of unprotected network activity...

Like I said, you're defining hashing wrong.  This is just the version hash, not the password hash or anything like that.  There are several different hashes used when battle.net logs on.