Rename Honorbuddy - A Guide for the Paranoid

even with the old 702 version this still gives me that BEX error weird

 

Its something related to the Dlls not wanting to play with a modified HB. I'll get a solution when I get home

 

maybe default with the option to change it to whatever we want, but not all the same, otherwise we get the same problem with blizz having the exact name that it is in processes.

 

you should NEVER modify or use modified honorbuddy executables. theres no guarantee that any protection measures built into the honorbuddy client will still continue to function as programmed once its been modified.

on top of that if there was ANY risk in leaving honorbuddy named honorbuddy, then it wouldn't be named honorbuddy and we would give you the tools or means to change it.

 

zonpan2lol
Can you please make a new tutorial that works with the 704er version?
Why constantly get error messages?
chrome.exe no longer works.
Please watch the new version and create a new tutorial.
So that we can start something with it, thank you.

 

What about hiding honorbuddy.exe process from task manager via a vb.net code or something. Would that do anything?

 

no, because wow isnt looking for it. same with the process name, theres no need because wow isnt programed to care what apps are running or what they are called. JUST if an app tries to mess with wow while its running.

 

I'm sorry folks, despite the mods disapproval I tried to find a solution but no possitive results.

I came to the conclussion that HB Auth servers are blocking any connection from modified versions of Honorbuddy.exe. The executable is still renameable but there is no way to make it work if you modify its internal properties.

It's not my fault, Auth servers are blocking the connection. They must have placed some kind of security to flag the executable as modified.


@CodenameG:

The title clearly says for the Paranoid. Have you considered the possibility that there's something you don't know or that you aren't aware of? What if you are wrong and you don't know it? I agree with you, I think you are right, but that doesn't mean I shouldn't try something in case you are wrong. The anti-detection security raises a good point, but I believe that should have nothing to do with the executable properties.

Have you seen World War Z? Where 11 people agree to one conclussion but there's one who takes measures in case they are wrong? Well, that's me, and many others in this forum. But obviously you are one of the 11 and I get it, you have to be a part of that group not because you want to but because you have to.

Anyhow, I was just trying to help the paranoid have one less thing to blame when they get banned. In some sort, I was helping you out.

Peace out.


----------

Again, sorry folks, feel free to close this thread since there's no way to pull it off now.

 

Would it hurt CodenameG to offer such a feature ANYWAY? Even if you're 100% convinced it's pointless, it would keep the tin-foil hat on those who want to wear it.

 

They will do anything to avoid having to work extra minutes

 

It would lead to "Where's Honorbuddy?" threads

 

Oh come on, do you think people are THAT stupid?

-No need for an answer.

 

BlindBossKey or HideWizard from seapsoft might do the trick. Did not test it and also agree to CNG that it makes no sense and might cause problems.

 

that would only work for windows 32 bit systems as 64bit has a different kernel system with patchguard. If you disable patchguard then it will work but its beyond what a basic user could do. Hiding a process with a 32 bit system is super easy but how many people still have 32 bit?

 

thank you

 

Really is this thread still going!?

Now you're attacking the developers for not giving something you want? Coercing the devs with the wisdoms as espoused by World War Z? Lol you couldn't make it up!

I think the community should show some respect.

HonorBuddy, arguably the most sophisticated publicly available bot, receives regular updates and is released when safe. Tripwire detection built in. A team of developers that not only give the community a mouth piece (that's the forums) but actually post threads and replies here often. So show some respect and dare I say, perchance listen to what they say?

If you want to contribute tips then fine but don't call out the developers for protecting their closed source product. If you don't like the fact you can't modify their executable then don't use it. Or go make your own, Einstein.

 

There's an unsuscribe button in the settings page. You should use that. I guess talking and expressing opinions on forums is now subnormal.

Also:

 

Exactly what I'm doing; matching your diatribe with my expressed opinion.

My opinion, in which case you didn't catch it, was that you show a lack of respect to developers. The rest is just rhetoric and out of context old re-hashed ideas -covered better previously.

PS quoting yourself only highlights your own aloofness.

 

Its not changing the description in task manager. I changed 2 of the application files and the shortcut to read what was on the first page but it still reads chrome.exe but the description says honorbuddy.

 

I do understand the OPs concerns but the question of changing the bots exe name has been around since 2006 when the first WOW bots came around. Back then the users/devs did not know much about Warden or detection methods that were used. Many bots came with the exe file changed to something different like notepad.exe. Despite all of this banwaves by the 10s of thousands of accounts still occured. Many bot developers and programmers who monitored warden stopped changing the exe name because of this.

Honorbuddy even with its flaws is the most advanced and complex bot ever released and has a proven track record of doing its best to protect its users. I have seen many banwaves with so many people reporting to the ban section the forurms were crashed for days. The devs here are the best and most experiened not to mention I am unaware of any other bot that is shipped with its exe file modified. Honorbuddy has an elaborate tripwire system that has prevented a major ban wave from occurring. The bans that we see today are not due to software detection, the cause is up for debate. If doing so would make a difference their is no doubt that that the devs would implement this change in a heart beat.

I do see your point but dont beleive that changing the exe name will do any good. Its been tried and proven many times over the years and gives people a false sense of security.