Quit crying about the "stolen" public code

[Deception]

I'm sick of reading thread after thread of people crying over the release of the precious NLS.dll.

You keep saying this code was never made public and therefore people should delete it and instead use BNLS.

I don't know about you, but it seems stupid to send your usernames, passwords and CD-Keys to a 3rd party server to be hashed when you can just do it locally with the PUBLIC code that has been released against the will of the author. NLS.dll is no longer private. Get over it.

[Warrior]

The point is it was released withought permission of the author(s) and no matter what you say that IS wrong.  BNLS is 100% secure as they get thousands of logons a day and I doubt they even care about one single password. They arn't exactly l33t h4x0rs that r0x Bnet y0. So with that said, you need to get over them being mad and refusing tooffer help with NLS.dll and if you dont like what you see on these forums do us all a favor and find some code to leech somewhere.

[Deception]

The point is it was released withought permission of the author(s) and no matter what you say that IS wrong.  BNLS is 100% secure as they get thousands of logons a day and I doubt they even care about one single password. They arn't exactly l33t h4x0rs that r0x Bnet y0. So with that said, you need to get over them being mad and refusing tooffer help with NLS.dll and if you dont like what you see on these forums do us all a favor and find some code to leech somewhere.

You fail to see the point. The point is, they need to stop bitching about people using their code. I think they should refuse to help people who ask for help with it, because anyone who can't figure out how to use it shouldn't be programming anyway.

However, the author(s) can't complain about it being public and they can't tell people not to use it when they were stupid enough to let someone "steal" it in the first place.

[Newby]

They didn't "let" someone steal it, someone *stupidly* left VNC running and, a retarded flaming newbie bruted his quite simple password, and stole it.

Therefore, although it is no longer private, the way it was released is lame. People who use it are just promoting stolen coding and products.

You know, I hope somebody steals your sources and uploads them, and then asks for help on how to modify it. Maybe you'll feel the same way.

EDIT -- Smart move removing "Mr. Kissass" from your post.

EDIT2 -- Also, without the "leaked" module that utilizes the NLS.dll, you'd have no fucking clue how to use it, because I doubt you could figure out the API declares all by yourself. Therefore, you are supporting leeched coding along with leaked products.

[Warrior]

Actually since the code IS property of the Author(s) I think they have sufficient rights to tell people not to use thier code but its up to the people to listen to them . Would you like something you worked very hard on to be leaked to the public and have about 20 people a day coming here asking for support, not getting it , being an idiot about it , and implementing it into thier bot with no respect torwards the author or even an acknowlegement ? I sure as hell wouldnt. Your the one thats whining over topics in the forums and frankly your looking like an idiot. Like I said before if you dont like what you read dont come to the Forums.

Edit: Spelling and fixed some sentences that didnt make sense.

[Deception]

Edit: Spelling and fixed some sentences that didnt make sense.

Your whole post doesn't make sense. You're an idiot to think that when given the option, people would rather continue sending their passwords and CD-Keys to BNLS than use someone's code because it is immoral.

If the authors of NLS.dll didn't want people using it, they shouldn't have written it.
If anything, the authors should be glad that people are using NLS.dll rather than being forced to give up their passwords and CD-Keys, hoping vL won't use them.

I'm sure Skywing and Yoni are glad they have loyal followers such as Warrior and Newby, who continue to give them an abundance of passwords and CD-Keys.

[Skywing]

Edit: Spelling and fixed some sentences that didnt make sense.

You're whole post doesn't make sense. You're an idiot to think that when given the option, people would rather continue sending their passwords and CD-Keys to BNLS than use someone's code because it is immoral.

If the authors of NLS didn't want people using it, they shouldn't have written it.
If anything, the authors should be glad that people are using NLS.dll rather than being forced to give up their passwords and CD-Keys, hoping vL won't use them.

I'm sure Skywing and Yoni are glad they have loyal followers such as Warrior and Newby, who continue to give them an abundance of passwords and CD-Keys.

Keep using BNLS. If you trust it...

Keep in mind that nobody ever forced anybody to use BNLS.

If we were in this for cd-keys and accounts, there would have been no reason to keep the system publicly available for such a long time.

[Deception]

Keep in mind that nobody ever forced anybody to use BNLS.

If we were in this for cd-keys and accounts, there would have been no reason to keep the system publicly available for such a long time.

Yes, but if someone wanted to use WarCraft III on a 3rd party client, they would have to either reverse it themselves (which not too many people can do) or use BNLS. Even if BNLS doesn't log passwords, you could have it do so and people who need WarCraft III bots would be forced to give you their information. It was a monopoly.

[Skywing]

Keep in mind that nobody ever forced anybody to use BNLS.

If we were in this for cd-keys and accounts, there would have been no reason to keep the system publicly available for such a long time.

Yes, but if someone wanted to use WarCraft III on a 3rd party client, they would have to either reverse it themselves (which not too many people can do) or use BNLS. Even if BNLS doesn't log passwords, you could have it do so and people who need WarCraft III bots would be forced to give you their information. It was a monopoly.

If people are unwilling to do work to get their client to work with Warcraft III, that's their problem.

I could have also just as easily not put it out at all in which case nobody else would have had third-party clients that worked on Warcraft III at all until somebody else spent the time to reverse it.  Would that have made you happier?

[Deception]

If people are unwilling to do work to get their client to work with Warcraft III, that's their problem.

I could have also just as easily not put it out at all in which case nobody else would have had third-party clients that worked on Warcraft III at all until somebody else spent the time to reverse it.  Would that have made you happier?

If BNLS wasn't public, I'm sure someone else would have reversed it and made it public sooner or later. But since BNLS was around, people figured it was pointless to waste time reversing it.

[Warrior]

Your making no sense, your saying not too much people can hash Warcraft III then your saying someone would come along and do it if BNLS didnt support Warcraft III Logons.  Thing is people already have reversed it for their private use-only. Does that mean that battle.net should release thier source just because they made it....? Hell no. You also fail to understand if BNLS were not trustworthy they would have done something already. I doubt if their intention was to obtain CDKeys and passwords that they wouldnt have held up so long. If you dont trust BNLS, dont use it but dont expect to flame them for getting mad over THIER CODE that was stolen. Also your saying im an idiot for if people giving the option would use BNLS over Local Hashing...not true. Think of it this way if people wanted to they could just use Local hashing for SC/BW/D2/LOD and forget about BNLS but BNLS still gets thousands of logons a day....are you getting it now? Or you could try this approach, I would rather have my bot be able to handle the new patch withought having to do anything to it except wait for BNLS to update, and I have no clue why your putting BNLS down. Hell, I doubt you could make such a reliable service and keep it running for as long as they have.  To end my argument it all comes down to one line
Leeching Code is WRONG
there is no way around it, no loophole, no anything. Authors reserve the right to openly flame / get mad about anyone using stolen code of theirs. If you have a problem with that I suggest you stop using BNLS if you still do, Hash Warcraft III yourself. I still dont get how you think its like if a little boy made a tree house and invited his neighbor but his neighbor decided to steal his other neighbors tree house instead of using one his first neighbor let him use. It shows that people who use the leaked code are stubborn and unwilling to learn. If you have anymore arguments to bring up against me please do as I am sure I have countered all of them.

[Michael]

Umm, Useing iago and userlosers and the rest of the authors stolen code is up to the user but it does show you have no respect for the people who are there to help you.

[iago]

Wow, I totally lost all respect for Deception.  huh..

Anyway, there's nothing I can do to stop people from using the code, since people like you suck.  But don't ask the authors of stolen code you're using for support.  Doing that is asinine.

[Newby]

Edit: Spelling and fixed some sentences that didnt make sense.

I'm sure Skywing and Yoni are glad they have loyal followers such as Warrior and Newby, who continue to give them an abundance of passwords and CD-Keys.

Who ever stated I use BNLS?

Also, you probably used to use BNLS. If they logged any information, I'm sure (if I was them) I'd steal everything of yours.

EDIT --

If the authors of NLS.dll didn't want people using it, they shouldn't have written it.

Yeah, I'm sure they knew it was gonna be stolen.

Of all things, I would thank the authors of the code for writing it, because I'm damn sure if it didn't get leaked, you'd be "sending an abundance of passwords and CDKeys" to BNLS. I also highly doubt (100%) you have any knowledge in assembly, and I higly doubt (500%) you could reverse the Warcraft III login sequence / hashing functions yourself.

[BaDDBLooD]

i think "wow" sums up this topic!

Deception, your opinion is invalid, bias, basically it's full of !@#$!