Please excuse my ignorance, but is tripwire protection included in HB or is this something I should run at the same time as HB. Granted I've purchased a Private Internet Access..not only for when I run HB but for other internet doings. This is to say, "hey, obviously the ISP for the computer you "caught" was here and I'm here!" But the post from Raphus, " Status Update as of 09:54 UTC 13.06.2013 Well, its time to open secret doors. Blizzard has stepped up detection in a big way since the 5.3 patch. We have been investigating their activity on detection and taking our time to make sure we got everything right. We didn't want to go public about this, because we thought they were targeting us directly. However, our latest finds shows that their new detection may affect other bots/tools. Therefore we highly suggest our community to not use any tools/hacks for WoW unless they have some kind of tripwire protection. You may forward the authors to us in case they need any assistance with the new detection methods. We have our tripwire protection extended for the new detection and we've been providing protection through the auth servers since patch 5.3. We mostly covered their new detection attempts and will probably do a beta release today or tomorrow. All the hate about delayed releases, I hope you guys understand why we delayed our 5.3 release and this hotfix release now. " This really got me nervous. So is Tripwire protection included?
Tripwire is built into Honorbuddy's auth servers. If the tripwire suspects WoW is detecting Honorbuddy, it cuts the auth servers and disconnects everyone.
This is a good thread because its something the HB dev's seemed to stress. Maybe an explanation of how this tripwire detection works would be handy as well.
It's probably hidden in the Desktop Battle.net client, good thing me and Blackbook said something ^^. They've tried this before... those old enough to remember of course.
I fed my brain with glucose and a flashing light bulb said "for bots". for changes of code, offsets, unsecured hack?s etcetc. Whatelse?
yea pls tell us everything about tripwire, so all the blizz guys who read in here will know... how about a /reboot brain?
You assume Blizz is so stupid that they can't get the bot and have their guys reverse engineer it the same way HB reverse engineers their Warden code.
Tripwire has been around since the days of Glider. I believe it was Hawker that brought it into this product. Tripwire is always active. It is constantly looking at Warden and will render all active sessions of Honorbuddy invalid if it detects Warden doing anything sneaky automatically. We can also activate Tripwire manually if we do not like what is happening currently. Rest assured that we keep your safety as our top priority.
How is a beta battle.net client even remotely related to the current issue at hand concerning detection? They upped their detection methods since 5.3, and last I knew, patch 5.3 had and has nothing to do with the battle.net client.. Or am i wrong? EDIT: For clarity, I'm NOT talking about the regular Launcher, but about the above mentioned 'battle.net client'
Everytime they update something in content they update their client. So it is not hard to add something in the client to detect certain things going on.
the "old" client is just before you start wow (meanwhile hb isn?t running) and i just think that warden (anti cheat / theft protection) is running as a sparate prozess if it does something suspectous it will trigger tripwire i.e. but since i got zero insight in any of the products iam just guessing
Isnt tripwire server side? How do you revers engineer server side application without hacking into it?
I don't think anyone we will have to worry about will discuss this too in depth since they're most likely developers of the bot and Honorbuddy is a closed source application just everything like plugins, profiles, combat routines can be created and modified.
