Quote (JiangyouNan @ 28 May 2012 16:49)
What you recommended is not a valid form of security. I ran possibly the largest log list back in 1.11-late 1.12 (obviously nothing compared to the whole d2hackit fiasco in I believe 1.09?), thousands of d2 account/password/cdkey info was on there. It was a working program that you yourself would hook onto d2 process and it would specifically ONLY read account/pw info and send it to my webserver. That being said, an easy way to counter this was to log into your account first and then inject said 3rd party program, however cdkeys would not be safe.
No AV vendor will ever detect this because it is so niche that it wouldn't make sense to provide security for it. Effectively making it undetectable.
Quote (Pulsing @ 28 May 2012 16:28)
LOL
how ironic considering how you spelled "authentificator"
Quote (Weeny @ 28 May 2012 16:12)
great guide, now nobody will get hacked on d3 after reading this! and i didnt know that all the d2 bots had viruses
Quote (JiangyouNan @ 28 May 2012 16:18)
Every program has the potential to have malicious coding embedded, not all Diablo 2 programs have "viruses", Bartoteck does not know what he is talking about.
Quote (JiangyouNan @ 28 May 2012 16:08)
trigs is not even a legitimate word to describe d2 third party programs.
\e should also point out you know nothing of what you speak of in regards to your post.
Hes the same user.. hes a gold thieff and keylogger , just trying to discreadit ur post OP
Hes trying to discourge ppl to follow ur method
This post was edited by RaWBOoGiE on May 28 2012 05:53pm