What's new
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

network detection

My approach(look at the connections) was from a unix-sysop which is my job. No magic anywhere. ;)

I still think the idea of different identifiers (open connection to buddyauth.com(IP), 32bit and a few others) is quite a good approach when the official statement is "we have no idea, yet".

Back in the day unix-sysops were regarded as dark magicians who messed with things man was not meant to know.:)
 
My approach(look at the connections) was from a unix-sysop which is my job. No magic anywhere. ;)

I still think the idea of different identifiers (open connection to buddyauth.com(IP), 32bit and a few others) is quite a good approach when the official statement is "we have no idea, yet".

B3rlin3r , Lets pretend this is what is happening, what approach would have to be taken by HB or the User to stop blizzard from being able to do this ?
 
From my point of view the easiest way to detect honorbuddy is to look at the client's open network connections. Like a "netstat /a" under windows...(even with non-priv. user rights)

So maybe your "a bit paranoid" online-auth.-system is a really bad idea?
When I used the bot on different comps I would get randomly disconnected all the time and it wouldn't even affect clients on the same computer. I felt like it was just too random to be an internet or a computer problem.
 
Back
Top