Slashdot Mirror


How bnetd Developers Reverse Engineered Battle.net

battlebot writes: "O'Reilly's ONlamp.com is running an interview with the bnetd developers that goes into great detail about how exactly they reverse-engineered Battle.net. This is by the same guy who wrote the recent Salon article, though is far more technical. They talk a little bit about their legal troubles too, and even sheepishly admit that perhaps talking to a lawyer earlier in the process would have been a good idea. Has this project been successfully squashed?"

16 of 221 comments (clear)

  1. The real question by Dynedain · · Score: 4, Funny

    The article says that they have made BNETD virtually indistinguishable from the real battlenet through reverse engineering. What I wanna know is, what function did they assign to the gem in the Diablo 2 client?

    --
    I'm out of my mind right now, but feel free to leave a message.....
    1. Re:The real question by Malicious · · Score: 3, Funny

      I think, that Blizzard should have an anti-trust lawsuit brought against them, for packaging the Battle.net connection software, in with their software, thus cripiling their competitors, and creating an online multiplayer monopoly.

      --
      01101001001000000110000101101101001000000110001001 10000101110100011011010110000101101110
    2. Re:The real question by nsanders · · Score: 3, Informative

      There is a GEM on network screen of D2. No one has any clue (does any one?) as to WTF it does. You press it, it says activated (or something. been a while since I played). You can turn it on or off. The joke is funny because we wonder what BNETD assigned it to do since no one really knows.

  2. Money talks... by brooks_talley · · Score: 3, Insightful

    Thing is, anyone with any kind of reasonable knowledge of law, patents, and copyright knows that the Blizzard lawsuit is, to be blunt, bullshit.

    Blizzard has no chance, or interest, in winning on the merits of their case. They know that open source developers have limited resources and are unlikely to mount a decent legal defense. So why not sue? It's not a legal decision so much as a strategic one: given the chance to squash potential future competitors for free, why not?

    It's a smart move on Blizzard's part. American IP laws favor corporations to such an incredibly laughable degree, it's amazing that Disney isn't suing everyone who uses a wheel (Steamboat Willie, 1928, and anyone who claims to have invented it before then had better have a notaraized motion picture).

    Bottom line: disgusting on the USPTO's part, dispicable on Blizzard's part, par for the course for the good old USA. Oh, wait, this is *good* for consumers. I must have missed that edict somehow.

    -b

  3. Battlenet Clone HowTO by DarkHelmet · · Score: 3, Funny
    ...that goes into great detail about how exactly they reverse-engineered Battle.net.
    1. Install packet sniffer on local network.
    2. Read lots of 1's and 0's into a huge dump file
    3. Familiarize yourself with UDP.
    4. Tear out clump of hair as stress relief.
    5. Create nifty diagrams that show the battlenet server as a black box with the game that you and your buddy have made online as the two other pieces.
    6. Look at the responses that the black box sends back to each of the machines.
    7. Ponder on whether or not a monkey would be a good programmer since a tail in addition to two hands that can hit those hard-to-reach keys.
    8. Create a prototype program that relays game packets from two client boxes.
    9. Play lots of StarCraft through this box.
    10. Debug lots and lots.
    11. Decide against implimenting cheats on the server box against your other cohorts that are helping you develop this
    12. Create a chat room interface.
    13. Do final testing on the program.
    14. Program into the server daemon random insult messages that will be sent to all of your friend programmers while testing, making them abandon the project out of anger.
    15. Profit.
    That was easy enough!
    --
    /^[A-Z0-9._%+-]+@[A-Z0-9.-]+\.[A-Z]{2,4}$/i
  4. Consulting an attorney earlier... by sterno · · Score: 5, Insightful

    If we assume for the moment that they had thought of consulting an attorney when they first embarked on this project, would it have made a difference? I mean, seeing as the DMCA didn't actually exist in '98, how could they have made some plan to defend themselves against prosecution under it. As for the straight up copyright issues, it's total hogwash, but at least they could have gotten the lawyerly advice of, "well they haven't got jack on you, but can you afford to fight it?"

    I was thinking about this earlier, and the really frustrating thing is how much of computer related tinkering seems to need to be run by a lawyer. I mean if you have a hobby like building kit cars, or constructing furniture, you have no need for attorneys. But if you want to get deeply involved in tinkering with software, etc, you suddenly need a law degree. Companies talk a lot about the damage that piracy has on the software economy, but I have to wonder how much more damage has been caused by the chilling effect on independent developers by this legal morass we call intellectual property.

    --
    This sig has been temporarily disconnected or is no longer in service
    1. Re:Consulting an attorney earlier... by markb · · Score: 5, Informative
      If we assume for the moment that they had thought of consulting an attorney when they first embarked on this project, would it have made a difference?

      Well, I did seek some legal device back in 1998, when I receive a cease and desist letter from the Software Publishers Association. The letter (well email, actually) came less than 12 hours after I published bnetd 0.1.

      The lawyer was from the Student Legal Services office at my university, and didn't know much about IP law, but I did seek legal advice early on. :)

    2. Re:Consulting an attorney earlier... by Seth+Finkelstein · · Score: 4, Interesting
      If we assume for the moment that they had thought of consulting an attorney when they first embarked on this project, would it have made a difference? I mean, seeing as the DMCA didn't actually exist in '98, how could they have made some plan to defend themselves against prosecution under it.

      This is addressed in the last part of the article:
      (emphasis added)

      Crittenden: We probably should have talked to a lawyer years ago to get an opinion on whether what we were doing was legal or not. I'm not sure how much it would have helped in this case. But it might have gotten us into a conversation with Blizzard much earlier, and perhaps in a less confrontational way.

      Sig: What Happened To The Censorware Project (censorware.org)

  5. blizzard's suing the wrong group by Frizzled · · Score: 5, Interesting

    warforge has been the team working on a warcraft 3 server (which caused all the problems with blizzard). they started with bnetd's code, but now the projects are basically separate.

    shame blizzard didn't do some research before turning the lawyers lose. even if they get an injunction against bnetd, they'll be shutting down the wrong group.

    _f

  6. They'll never get another dollar from me. by NoMoreNicksLeft · · Score: 5, Interesting

    I have legimate copies of every game/expansion pack they've ever produced, on up to Diablo II. Full retail price, too, not bargain bin or second hand. They _were_ the one company that you could be sure I would buy a game from, maybe not the day it was released, but I'd get it eventually.

    As I remember it, this news hit the very day that I couldn't hold out any longer for D2. Strangely, I'd never heard of bnetd until then. Being able to play on a server I could control though, would only have encouraged me even more, to buy their games. I had only played Diablo I on Battlenet once or twice, and not been at all happy... nice idea, but too many assholes. To think that I could fix that problem without extending several dozen ipxtunnels, etc... that is kickass.

    They should have hired these guys, not sued them. That would have been a cheaper way to stall bnetd, they would have gotten more for their money, and they wouldn't have pissed people like me off.

    Fuck you, Blizzard.

    To everyone on the bnetd team, keep kicking ass, and the best of luck to you.

  7. Yeah, bnetd is TOTALLY DEAD. by Wakko+Warner · · Score: 4, Funny
    --
    "Remember when the U.S. had a drug problem, and then we declared a War On Drugs, and now you can't buy drugs anymore?"
  8. Wrong target by sher0209 · · Score: 3, Informative

    It's unfortunate that Blizzard is targeting BNETD. The problem that Blizzard is facing, is leaked copies of the Warcraft III beta being played all over the internet. Every beta tester got a unique CD-Key with their copy of the beta, to play on Battle.net you needed a unique key (i.e. one that was not being used).

    The people with pirated copies of the beta want to play too, and since there's no single player in the beta, they need a Battle.net server to connect to. Now, Blizzard isn't about to let 10,000 illegal copies on to their server so the people running stolen copies turned to BNET.D.

    At this time, through some strange coincidence, BNET.D attracted the attention of Blizzard. BNET.D said "Ok, game pirates suck, we won't develop Warcraft III compatiblity", got sued, and pulled their code. A handful of the contributers of BNET.D wanted to keep pursuing WC3 and formed Warforge.

    Granted, there is a point or two in favor of developing a BNET.D server for WC3:
    [] Warcraft III doesn't allow for LAN play
    [] I forgot the second one
    They've been keeping up with Blizzards efforts to disallow use on non-battle.net servers very well (a patch is usually out in less than two days).

    As for my opinion: People are going to find a way to play/use the latest and greatest software without paying for it. Period. The more attractive it is, the faster it will be cracked. Companies need to realize this and make software more available (public betas, lower prices, no prices (free)...) Even then, people will find ways to get products for free, but just like the music industry is starting to realize, people will take path of least resistance to the software they want.

    That's my $0.03
    --
    dan

    --
    -- dan.sherman
  9. underground programming. by Restil · · Score: 4, Insightful

    Its getting to the point where the open source movement will move further and further underground. All the benefits of the open source would still remain if the lead developers remained anonymous (except maybe for ego purposes). Nobody ever has, and probably won't challenge the majority of open source software, but why risk it anymore. Let the software companies and the movie industry waste a large sum of money trying to silence the small insignificant factions. If those factions ever do rise to power and the power bases lose their market as a result, then in time, most of this won't even matter.

    Take Microsoft and the northwest schools. It is not just ONE school district talking about mass migration here. If they do it, and pull it off, other districts will notice. They'll see that it actually CAN be done. They'll see that there really IS support available, and they'll see that it IS saving a lot of money, and they can safely tell the BSA to fuck off. They'll switch too. One at a time, one after another. Microsoft will lose them all. Now you have a whole bunch of high school students, ALL of them trained on linux or whatever open source suite appealed to the districts. They go off to college. You will now see the same movement there. And once that wave is done sweeping through, the corporate world is next. It really COULD start with one school district, and in 10 years, Microsoft will have completely lost their grip on the market, never to regain it.

    The point is, after a few years of this, everyone will be using open source software to some degree. People will EXPECT software to be free. And when Blizzard, or the movie industry or anyone comes along and sends out letters saying "you can't use that software" a whole lot of regular non-geek people will turn around and say "up yours!" to the respective finger pointer and tell them where they can shove it and take their money elsewhere.

    The music industry is already learning the hard way on this. They had their chance. They could have completely cornered the online market for years had they put in place a simple, inexpensive, non-intrusive music distribution system YEARS ago when they had the chance. But no, they were so concerned about rampant piracy and how it might affect their bottom line, they instead played stupid legal games to attempt to stifle the music trading. And for all the court cases, and all the laws that passed, trading has increased to massive proportions. They sue napster into the ground, 10 others pop up to take its place, only non-centralized and no way to easily shut them down. Who do you go after now? the programmers??

    Well, you can't if you don't know who they are.

    So undergound all this even potentially murky legal stuff. Wait a few years. All those who would threaten you will be overcome by the wave, and afterwards, they wouldn't dare.

    -Restil

    --
    Play with my webcams and lights here
    1. Re:underground programming. by Seth+Finkelstein · · Score: 5, Interesting
      All the benefits of the open source would still remain if the lead developers remained anonymous (except maybe for ego purposes)

      It is EXTREMELY stressful to be an anonymous developer for legal-risky work. Let me tell you, I know.

      As Jon Johansen said, in an old interview about DeCSS:
      (emphasis added)

      http://www.linuxworld.com/linuxworld/lw-2000-01/lw -01-dvd-interview.html

      Jon Johansen: I'm 16 now, I was 15 when it happened ... and the encryption code wasn't in fact written by me, but written by the German member. There seems to be a bit of confusion about that part.

      LinuxWorld: The other two people that you had worked with to make the player are remaining anonymous -- is that right?

      Jon Johansen: Yes, that is correct.

      ...

      LinuxWorld: Do you know why they want to remain anonymous?

      Jon Johansen: They are both a lot older than me, and they are employed. So I guess they just didn't want the publicity, and they were perhaps afraid of getting fired.

      Sig: What Happened To The Censorware Project (censorware.org)

  10. Attacking the Hydra by _Sprocket_ · · Score: 3, Insightful


    shame blizzard didn't do some research before turning the lawyers lose. even if they get an injunction against bnetd, they'll be shutting down the wrong group.


    That was my first reaction too. But after giving it some additional thought, I have come up with a reason the Blizzard/Vivendi legal team might be acting with more insight than it appears to at first blush.

    There are several theories as to why Blizzard is taking action now. Possible movement of battle.net to a subscription service. Blizzard's announced future offering of World of Warcraft, certainly to be a subscription service. And the new release Warcraft III which is supported by the bnetd fork called Warforge. And there's the key. Warforge is a fork. A spinoff. Further development of a project that has been an annoyance to Blizzard since 1998.

    If Blizzard managed to kill Warforge, what is to stop another group from retracing those footsteps and modifying bnetd again? What about fans who decide they don't wish to continue paying a subscription to World of Warcraft and use bnetd as a basis for a new, freely available alternative? What if battle.net goes pay-to-play and private and public bnetd servers offer a much more attractive alternative?

    The fact is that bnetd makes a very sensible target to head off all these possible forks. And once the legal groundwork is laid in killing bnetd, it would be trivial to send out cease-and-desist letters to those whose work is based on bnetd.

    Sure. It will be almost impossible to wipe bnetd off the face of the net. But development is going to slow down considerably if bnetd source code is just as illegal as a warez copy of Warcraft III.
  11. Re:It really sucks. by baywulf · · Score: 4, Funny
    Compaq had to pick virgin programmers that had no knowledge of IBM's code.


    AI think it is safe to assume more programmers are virgin.