Reconnections

[Topaz]

Will you get ipbanned by reconnecting every 3 seconds?

This is just to settle an argument HackeZ and I had about him testing all the possible cdkey combinations.

[Blaze]

I would say yes if your connecting from the same IP each time.

[iago]

Yes, I'm pretty sure you do. 

[Warrior]

This is just to settle an argument HackeZ and I had about him testing all the possible cdkey combinations.

Buahahahah

You know how long that would take?

[BaDDBLooD]

This is just to settle an argument HackeZ and I had about him testing all the possible cdkey combinations.

Buahahahah

You know how long that would take?

Yes i do ~

[Yegg]

You would get ipbanned if you were using 30 seconds instead of 5 seconds on the same IP. Of course it would take much longer. I've tested this before.

[MyndFyre]

What if you varied the NAT local IP?

(DWORD)       Protocol ID (0)
(DWORD)       Platform ID
(DWORD)       Product ID
(DWORD)       Version Byte
(DWORD)       Product language
(DWORD)       Local IP for NAT compatibility*
(DWORD)       Time zone bias*
(DWORD)       Locale ID*
(DWORD)       Language ID*
(STRING)     Country abreviation
(STRING)     Country

(SID_AUTH_INFO client to server)
I find it hard to believe that Blizzard would screw up a large group that could potentially have a lot of login attempts all at once from the same external IP.  Has this been tested?

[Eric]

What if you varied the NAT local IP?

(DWORD)       Protocol ID (0)
(DWORD)       Platform ID
(DWORD)       Product ID
(DWORD)       Version Byte
(DWORD)       Product language
(DWORD)       Local IP for NAT compatibility*
(DWORD)       Time zone bias*
(DWORD)       Locale ID*
(DWORD)       Language ID*
(STRING)     Country abreviation
(STRING)     Country

(SID_AUTH_INFO client to server)
I find it hard to believe that Blizzard would screw up a large group that could potentially have a lot of login attempts all at once from the same external IP.  Has this been tested?

There is no way to bypass the protection and it's set up in such a way that it would be very hard to trigger without doing something that you were not supposed to do be doing.

[NetNX]

What if you varied the NAT local IP?

(DWORD)       Protocol ID (0)
(DWORD)       Platform ID
(DWORD)       Product ID
(DWORD)       Version Byte
(DWORD)       Product language
(DWORD)       Local IP for NAT compatibility*
(DWORD)       Time zone bias*
(DWORD)       Locale ID*
(DWORD)       Language ID*
(STRING)     Country abreviation
(STRING)     Country

(SID_AUTH_INFO client to server)
I find it hard to believe that Blizzard would screw up a large group that could potentially have a lot of login attempts all at once from the same external IP.  Has this been tested?

There is no way to bypass the protection and it's set up in such a way that it would be very hard to trigger without doing something that you were not supposed to do be doing.

Well cdkey 'scanning' wouldn't be able to happen in 3 second intervals since your usually IPBanned for 15-30 minutes for getting an invalid cdkey and even longer then that for getting aditional bans in the time after unban

this is how i would go about doing it.. find as many Valid/Banned/Muted/Voided('VBMV') ect keys that arent invalid find the working keygen code to make a VALID key to install starcraft with then check that key with your list of 'VBMV' then have them connect via proxys to battlenet and check the randomly generated keys then your only limiting factor would be how many proxys you could find (note connect each proxy to all 4 servers useast uswest asia europe) also only scan keys that start with 0-5 because keys will never have a number higher then that (from what ive seen correct me if im wrong)

[Ban]

Will you get ipbanned by reconnecting every 3 seconds?

This is just to settle an argument HackeZ and I had about him testing all the possible cdkey combinations.

HackeZ and I were discussing this last night. IIRC the time period in which he was scanning for keys was early 2000/late 90s, when the restrictions were FAR less. You could scan for hours upon hours and not get ipbanned (Assuming you don't hit an invalid key [cdkey testing], I don't remember if you were ip'd immediatly for invalid keys back then or not). On the same note, it used to be possible to bypass IP banning in this way:

Connect using IP instead of X.battle.net
Send Key
Receive Invalid Key, Connection is closed.
Quickly rotate to a differn't IP that is under X.battle.net

I'm pretty sure the reason this worked was because it took a bit (30 or so seconds) for the other servers to be notified of the IP ban, which goes back to the horrible netcode Blizzard used to have (splits up the anus). I'm not sure if this is still possible as the netcode has improved immensily.

I also have a feeling that the message sent to the servers contains a timestamp of when the IPBan was issued. Why do I think this?
Because upon connecting AFTER the ipban was issued, once the servers were notified, I think that the one I had connected to would notice "oh hey, he connected after the ipban, maybe there was some sort of problem here?" and drop the ipban on all servers.

Again, I am not sure as to whether or not this is still possible. Perhaps someone feels like taking the time to test this?

[UserLoser.]

Will you get ipbanned by reconnecting every 3 seconds?

This is just to settle an argument HackeZ and I had about him testing all the possible cdkey combinations.

HackeZ and I were discussing this last night. IIRC the time period in which he was scanning for keys was early 2000/late 90s, when the restrictions were FAR less. You could scan for hours upon hours and not get ipbanned (Assuming you don't hit an invalid key [cdkey testing], I don't remember if you were ip'd immediatly for invalid keys back then or not). On the same note, it used to be possible to bypass IP banning in this way:

Connect using IP instead of X.battle.net
Send Key
Receive Invalid Key, Connection is closed.
Quickly rotate to a differn't IP that is under X.battle.net

I'm pretty sure the reason this worked was because it took a bit (30 or so seconds) for the other servers to be notified of the IP ban, which goes back to the horrible netcode Blizzard used to have (splits up the anus). I'm not sure if this is still possible as the netcode has improved immensily.

I also have a feeling that the message sent to the servers contains a timestamp of when the IPBan was issued. Why do I think this?
Because upon connecting AFTER the ipban was issued, once the servers were notified, I think that the one I had connected to would notice "oh hey, he connected after the ipban, maybe there was some sort of problem here?" and drop the ipban on all servers.

Again, I am not sure as to whether or not this is still possible. Perhaps someone feels like taking the time to test this?

When setting the server to "X.battle.net", all the bot does is resolve "X.battle.net" it to it's IP address(es)... so that doesn't make a difference

[iago]

When setting the server to "X.battle.net", all the bot does is resolve "X.battle.net" it to it's IP address(es)... so that doesn't make a difference

Quickly rotate to a different IP that is under X.battle.net

Perhaps when he said a "different IP" he meant to use a ... different IP?

And we can be reasonably sure that a different IP is a different computer (not necessarly, but usually), so all the rest of the stuff he said might apply.

[UserLoser.]

When setting the server to "X.battle.net", all the bot does is resolve "X.battle.net" it to it's IP address(es)... so that doesn't make a difference

Quickly rotate to a different IP that is under X.battle.net

Perhaps when he said a "different IP" he meant to use a ... different IP?

And we can be reasonably sure that a different IP is a different computer (not necessarly, but usually), so all the rest of the stuff he said might apply.

Huh.  What I said makes sense...

[raylu]

uswest:
w.x.y.z
a.b.c.d

Connect to w.x.y.z for a while, get IPBanned, swith to a.b.c.d. That's what he meant. x.battle.net is not an IP.

[UserLoser.]

uswest:
w.x.y.z
a.b.c.d

Connect to w.x.y.z for a while, get IPBanned, swith to a.b.c.d. That's what he meant. x.battle.net is not an IP.

Depending on what x is, it can resolve up to 33 known IP addresses.