CD-Key Exception

[Lance]

Just updated to 2.1.2 (with the new BNetLogin.jar), tried to connect (W3XP) and got the following error:

Code: [Select]

CRITICAL: [BNET] Caught exception while validating CD-Keys: exceptions.LoginException: CDKey is not 24 characters!

Thanks for the help

[Blaze]

Is your cdkey 24 characters? 

[Lance]

No; both the WAR3 and W3XP keys are 26 characters. 

[Lance]

I am looking inside BNetLogin.jar and I see Alpha24Decode.class. I guess this plugin wont work!  

[Lance]

I got lazy and downloaded the latest javaop2 and bnetlogin projects and undid the renaming then exported the bnetlogin jar. I am not getting the 24-character key error anymore but I am getting this:

Code: [Select]

... JUNK ...

[18:18:36.482] INFO: [BNET] Calculated. Sending version check..
[18:18:36.580] Login Exception:
[18:18:36.593] exceptions.LoginException: [BNET] Wrong product value for your CD Key
[18:18:36.595] packets.SidAuthCheck.checkIncoming(SidAuthCheck.java:153)
[18:18:36.595] PluginMain.processedPacket(PluginMain.java:268)
[18:18:36.610] pluginmanagers.PluginRegistration.processedIncomingPacket(PluginRegistration.java:698)
[18:18:36.617] bot.PacketThread.run(PacketThread.java:173)


[Joe]

Did you download the updated BNetLogin jar?

[Lance]

Yes

[Lance]

By the way, why are the "server", "port", and "connect automatically" settings not in the BNetLogin plugin? Without the BNetLogin plugin, they are useless.

[jays]

I'm still getting this error, how do you fix it?

[Lance]

We are waiting on our maintainer for the fix

I was feeling lucky so I imported the javaop2, bnetlogin, channel list, and swing gui packages from the svn and exported them. From there, I imported the CommandLineConfiguration jar from 2.1.2 and refactored some of the util class names (to comply with the new class names in 2.1.3), and jar'ed that too. Next, I ran the cmdlineconfigure jar, set up a bot with only the three previously mentioned plugins, saved my bnetlogin settings, reloaded the bot, and tried to connect. The bot is still a little rough around the edges because it is in development, but the problem from the old BnetLogin plugin persists... Take a look:



Nothing funny with the stack trace except for this:

Code: [Select]

Exception in Metacity for theme "Nodoka": Variable "mini_icon_width" not defined
But I am positive it has nothing to do with the BnetLogin problem.

[Joe]

I'm proud of you. Nobody else follows SVN as far as I know.

The issue, I believe, is something to do with the fact that KEYLEN was marked final. You can thank Ron for that. Well, he didn't make the ruhtard move of making it 24, but eh?

Anyhow, I'm so far past 2.1.2 that unless anyone wants to be a saint and recompile the entire bot for me, this will wait until 2.1.3, but since like 50 of you have complained (I didn't know that many of you used JavaOp still!), I'll make that my #1 priority project, which admittedly doesn't mean much.

If it's not out by this Saturday, please annoy me. Especially via IM.

[Joe]

Try the SVN now. If that doesn't work, I'm working on a full reversal of StarCraft's 26-char key methods. In fact, even if it does, I'm going to use the new code because I like it better.

Make sure you recompile the entire bot. Just go to your svn folder and type 'ant'.

[Lance]

That resolves the key length issue but not the product value one

Thanks

[Joe]

Well cool, that's like the deck integrity on an aircraft carrier being enough so a plane can land, but it still can't float!

I'm working on reversing StarCraft's decoder as we speak.

[Lance]

Is the b43 BnetLogin plugin archived somewhere? iago had a link up for b43 but it's dead now