Sorry to bump this.

[quote]1.) You still need to have the file time before you make the request.
2.) Why would you need to specify the key length?  All Starcraft keys have the same length, all Diablo 2/W2BN keys have the same length, and all War3 keys have the same length.  Wouldn't it know by your client ID ('STAR', 'WAR3', etc.) how long the damn key length is?
3.) What is the "cd key product id" ?  Is that the client ID -- thus the same as the client ID in the first packet?
4.) What is the "cd key public value" ?  I've re-checked the BNLS protocol spec and can find nothing on it.
5.) What if you're logging on with W3XP?  Do you only hash the WAR3 key?[/quote]
1) You don't, its for resume only, so you don't resume an older version of the file.
2) The same reason you need to specify that theres two keys in a D2XP/WAR3 logon. None at all =p.
3) See DecodeSCKey
4) See DecodeSCKey
5) D'no.

[quote author=Joe link=topic=7517.msg132807#msg132807 date=1131071839]
3) See DecodeSCKey
4) See DecodeSCKey
5) D'no.
[/quote]

What?

CDKey Product ID is found in DecodeCDKey
CDKey Public Value is found in DecodeCDKey
I don't know about WAR3 hashing.