Messages

1

JavaOp Support Archive / Re: i constantly get this...

« on: September 26, 2007, 04:02:39 am »

The error was on USEast with Diablo 2: Lord of Destruction, though I might have tried StarCraft and WarCraft 2 a few times as well. No Greets configured, and the following plugins:

Antiflood
Email Registration Plugin
Ping Plugin
Commands
Basic Commands
Channel list plugin
Simple event processor
Help
Connection Commands
Battle.net Login Plugin
Console Display Plugin
Version plugin
ChoedanKal (this is one of my own, connects to my website and sets Bot permissions accordingly)

2

JavaOp Support Archive / Re: i constantly get this...

« on: September 14, 2007, 07:46:25 am »

I have experienced similar problems, and from what I can tell, the following is going on:

1: JavaOP connects normally, and starts doing bot stuff
2: After a couple of minutes, JavaOP suddenly disconnects and is unable to reconnect (above error)

I couldn't figure out what was going on until it happened while I was playing StarCraft in the mean time - I suddenly got a "you have been disconnected from Battle.net" notice. Subsequent attempts to log in again resulted in "Connecting..." after which I was thrown back to the realm selection screen. Other realms work fine after this, but I can't get back on USEast. Short explanation: temporary IP ban on any realm I try to use JavaOP on.

3

JavaOp Support Archive / Re: What ports should I open on my firewall?

« on: March 22, 2007, 12:24:22 pm »

It seems the solution to my problem was the order in which I configured my /etc/shorewall/rules file. For some reason it ignores ACCEPT rules after I start giving DNAT rules (if that means anything to anyone).

Why, may I ask, are you blocking outgoing ports?  Are you afraid one of your programs is going to attack someone else?

The same reason I block incoming ports: I don't want anything on that box to do anything related to the internet unless I say so. The box is connected to the internet 24/7 - it never hurts to be paranoid about security.

I don't know of any software firewall that doesn't prompt you when a local application tries to access the internet so neither of those reasons hold any merit.

Let me guess, you are a Windows user?

I use Shoreline firewall, which is a front-end to IPTables, and runs "in the background" with a text file containing rules. When something related to the internet happens, it checks those rules what to do, and if there are no rules for this situation, it does it's default behavior: it drops the connection (you could set it to accept, but that'd defeat the purpose of the firewall).

This might be difficult to grasp, but the box I'm running my bot on doesn't have a screen, nor anything remotely resembling a graphical interface (unless you count my 1337 shell colors), so "prompting the user" is without meaning on my machine, since there's only a user logged in about 0.5% of each day.

4

JavaOp Support Archive / [Solved] What ports should I open on my firewall?

« on: March 21, 2007, 07:17:52 pm »

I'm currently blocking all outgoing ports except those I explicitely open on my Linux box. Now, when my firewall is on, I get this:

Code: [Select]

Tysan: [23:08:04.463] NOTICE: Bot 'Tysan' has been started.
Tysan: [23:08:04.464] DEBUG: Entering disconnect()
Tysan: [23:08:04.464] DEBUG: Entering connect()
Tysan: [23:08:04.504] INFO: Trying BNLS server: bnls.valhallalegends.com
Tysan: [23:08:04.526] INFO: Resolving ip for server: useast.battle.net
Tysan: [23:08:04.553] INFO: Resolves to 12 different addresses
Tysan: [23:08:04.554] INFO: Choosing address 6 [useast.battle.net/63.240.202.138]
Tysan: [23:08:04.554] INFO: Attempting to connect
Tysan: [23:08:04.777] INFO: Connected to /63.240.202.138:6112
Tysan: [23:08:04.780] INFO: Trying BNLS server: bnls.valhallalegends.com
Tysan: [23:08:04.789] INFO: Connected to useast.battle.net:6112
Tysan: [23:08:04.789] INFO: Sending protocol byte (0x01).
Tysan: [23:08:04.790] INFO: Switching to Binary protocol.
Tysan: [23:08:04.791] INFO: Sending authorization.
Tysan: [23:08:05.151] ERROR: Connect failed: java.net.SocketException: Connection reset

Though I can connect just fine when I tell the firewall to clear (ie allow everything). I'm using Shoreline Firewall, and I have opened ports 6112 and 6113 (tcp and udp) for Battle.net, as well as port 9367 (tcp) for BNLS. Is there anything else I should open to correctly sign in?

5

JavaOp Support Archive / Re: Does anyone want to be the new maintainer?

« on: March 21, 2007, 03:59:10 am »

I personally don't have time to take over any projects (and lack much understanding of the Battle.net protocol as a whole, though I do know a few things), but I due to JavaOP's plugin system I don't really consider this a problem. If I want a new feature I can easily write it myself, and as long as someone ensures the bot as a whole stays connected to Battle.net it all works for me.

6

JavaOp Support Archive / Re: Battle.net says wrong password, I say otherwise

« on: March 01, 2007, 04:38:57 am »

Try making a password that's all uppercase. Does it work?

No

Try making a password that's all lowercase. Does it work?

Yes

Try making a password with mixed cases. Does it work?

No

---

All three tests used the same password, with the first being all lowercase, the second all uppercase, and the third alternating upper/lowercase

Hope this helps

7

JavaOp Support Archive / Re: Battle.net says wrong password, I say otherwise

« on: February 27, 2007, 12:46:31 pm »

Can you login alright with the client or a different bot?

Haven't tried any other bots - most bots I know use BNLS for everything and I don't like my CD-Keys going across the wire in plain text.

The real client lets me login just fine, tried it with several accounts actually.

You're not the first one to report a broken password.

Might it have something to do with the length of the password? Both accounts I tried used a 12 character password, perhaps it gets truncated by one of the algorithms?

Try making a new account with the client and try passing with JavaOp.

Made a new account with the client, 5 character password, connects without a problem. Next, changed the password of my old account to something slightly smaller (11 chars), same problem, changed it to 8 chars, still the same problem. Changed it to 6 chars, without alternating lower/uppercase and no numbers: login works.

Try making a new account with JavaOp.

I made a new account with the same difficult password my old account has, and this time it did log in - relogging also works.

Since you're the second one to bring this up I'm kind of reluctant to say this but I want to guess you have the wrong password.

No need to be reluctant, this was of course one of the possibilities, so let's summarize:

1) Old password doesn't work, slightly smaller variations either don't
2) Password of 6 chars with just lowercase does work
3) New account by WarCraft 2 client with simple password does log in (haven't tried new account with complex password)
4) New account by JavaOP with difficult password does log in

8

JavaOp Support Archive / Battle.net says wrong password, I say otherwise

« on: February 26, 2007, 03:05:33 pm »

I'm using JavaOP 41 beta, trying to connect as a WarCraft 2 client

Code: [Select]

[20:55:31.593] INFO: Trying BNLS server: bnls.valhallalegends.com
[20:55:31.640] INFO: Resolving ip for server: useast.battle.net
[20:55:31.656] INFO: Resolves to 12 different addresses
[20:55:31.656] INFO: Choosing address 9 [useast.battle.net/63.240.202.138]
[20:55:31.656] INFO: Attempting to connect
[20:55:31.875] INFO: Connected to /63.240.202.138:6112
[20:55:31.890] INFO: Trying BNLS server: bnls.valhallalegends.com
[20:55:31.890] INFO: Connected to useast.battle.net:6112
[20:55:31.890] INFO: Sending protocol byte (0x01).
[20:55:31.906] INFO: Switching to Binary protocol.
[20:55:31.906] INFO: Sending authorization.
[20:55:32.281] INFO: Authorization sent, waiting for reply.
[20:55:32.281] INFO: Beginning to receive packets
[20:55:32.812] INFO: CDKey and Version check sent.
[20:55:32.921] INFO: CDKey and Version check successful.  Attempting to log in.
[20:55:33.125] Bot tried to use an invalid password.
[20:55:33.140] exceptions.InvalidPassword: Login failed -- invalid password.
[20:55:33.140] Login.checkLogonResponse(Login.java:302)
[20:55:33.140] PluginMain.processedPacket(PluginMain.java:345)
[20:55:33.140] pluginmanagers.PluginRegistration.processedIncomingPacket(PluginRegistration.java:722)
[20:55:33.140] bot.PacketThread.run(PacketThread.java:179)

The SID_LOGONRESPONSE2 I am receiving:

Code: [Select]

ff 3a 08 00 02 00 00 00

According to the Bnetdocs page about 0x3A I found in Google's cache this is indeed the packet that says I am trying to give it the wrong password, but I'm certain I'm using the right password, so my guess is that there's something wrong with the way the password is sent.

That same page also tells that SID_LOGONRESPONSE2 (0x3A) is meant for Diablo 2 and LoD, not for WarCraft 2 (which according to my Google skills should be SID_LOGONRESPONSE (0x29)), of course, this information may be out of date, and one of the replies says 0x3A is also possible.

If I understood the JavaOP source correctly, this is what is being sent to Battle.net:

(DWORD) Client Token
(DWORD) Server Token
6x (DWORD) Password hash
(NTSTRING) Username

So, an error in the hashing algorithm perhaps?

9

JavaOp Support Archive / Re: About the whole RCRS and BNLS thingy

« on: February 25, 2007, 07:53:29 am »

you're referring to me stating that local CheckRevision was re-enabled for W2BN

Yeah, got the whole thing confused it seems.

10

JavaOp Support Archive / Re: About the whole RCRS and BNLS thingy

« on: February 23, 2007, 09:38:16 am »

Hdx, I don't suppose your server supports WarCraft 2 logins? And I understand the standard version of JBLS isn't rigged to do anything with CD-keys and passwords - wouldn't be good for your reputation

Anyway, I've been trying to connect for about an hour now, BNLS is down so that obviously doesn't work, and I'm getting invalid password notifications when using alternatives.

So I'm guessing I'll have to wait until BNLS gets back online. Tried some alternatives that were posted on the Stealthbot forums (by Hdx no less ), but that didn't work out either.

Does beta 41 even support WarCraft 2 at the moment? Seem to recall some part of the 42 patchnotes that mentioned it being disabled, or I might have read it too fast.

In any case, thanks for your help, both of you of course

11

JavaOp Support Archive / Re: About the whole RCRS and BNLS thingy

« on: February 22, 2007, 05:08:01 am »

Ok thanks for clearing that up - I must admit I haven't looked at the source beyond the BNETLogin plugin

12

JavaOp Support Archive / Re: JavaOp2 -- Beta 41b

« on: February 21, 2007, 06:40:33 am »

javac -source 1.4 -target 1.4 MyClass.java

Works with any JDK >= 1.4

13

JavaOp Support Archive / About the whole RCRS and BNLS thingy

« on: February 21, 2007, 06:09:31 am »

Greetings,

first of all congratulations to Joe and iago on a great job. I absolutely love JavaOP, and have used it with great pleasure in the past.

I may be using it again in the near future, but there are a few questions I have first. Since RCRS has been removed from JavaOP and replaced by BNLS, I am wondering about the following:

For what tasks in the login process is BNLS used? One of the main advantages of RCRS was that it did not send any private data (CD keys, passwords) across the network, which most BNLS-based bots do. From what I recall BNLS can be used in this way as well - does the current version of JavaOP only use BNLS for the things it used RCRS in the past, or does it do more?

Edit: I just took a look at the source and it seems the latest versions use BNLS for pretty much everything. I haven't been following the whole Bot Development scene for a while, but from what I understand the whole new "lockdown" thingy only affects the Checkrevision part. Would it be possible for me to modify the Login procedure so it only uses BNLS for the Checkrevision and do everything else locally? (similar to the way I believe RCRS was used in the past)

With regards,

TyC-Pros