Keyclone - Got an email from a Blizzard friend

Quote:

---

Warden scans Inprocess, so anything modifying either WoW files or memory will be detected.

---

ok, i'll play.

as per the wow forums, it is normal to modify the config.wtf. i have confirmed what is stated in this post that:

http://forums.worldofwarcraft.com/th...107534&sid=1#4

there are blue posters (GMs) that recommend or endorse modifying the config.wtf file.

your statement that warden looks to see if anything has modified the files... while being 'in process'... would solve the issue right there. the config.wtf file is modified PRIOR to executing wow.exe. as such, as far as warden is concerned, the files are not changed during runtime.

seems to me, EvilSeed is just trying to spread (evil) seeds of doubt

Quote:

---

Originally Posted by henrik.falk

As someone who actually knows how to program, that's just wrong.
On so many levels.

---

Care to explain?

Quote:

---

Originally Posted by henrik.falk

Anyho, trying to hide from Warden would pretty much seem like
we are admitting that we are doing something fishy.
Better just keep a dialogue open with Blizzard.

---

I totally agree, some of the 'grey area' parts of Keyclone should be temporarily suspended until we can enter into a proper dialogue with someone who is capable of making these sorts of decisions on behalf of Blizzard (i.e someone higher than a GM). If Blizzard see us to be cooperative with them then we are far less likely to ever have any punishments brought against individuals for Multiboxing.

Quote:

---

Originally Posted by Keyclone

seems to me, EvilSeed is just trying to spread (evil) seeds of doubt

---

Whilst I hope this is the case, it would be sensible for every eventuality, we don't want to get caught with our pants down and end up with a lot of our community getting banned just because we didn't heed the warning.

As an additional note, I believe Blizzard would give us fair warning if Keyclone were to become "illegal" however I find it far more likely that AutoHotKey would be their 'prefered' target, simply because of the scriptable nature of it.

P.S. Links to Lax's blog about warden and warden-net.

http://onwarden.blogspot.com/
http://www.ismods.com/warden/

I hope these provide some info - more than the Greg Hoglund posts do anyway.

Quote:

---

until we can enter into a proper dialogue with someone who is capable of making these sorts of decisions on behalf of Blizzard (i.e someone higher than a GM).

---

in the works...

Remember it all comes down to the user... if we use keyclone legitimately then we should be safe.

I have a G15 and that can be used very effectively for botting and other activities contrary to the TOS as can most of the devices that give additional keys and come with macro software.

From the FAQ Linked:
No. ProcessGuard will prevent Warden from having certain access to programs that it shouldn't, but Warden will still be able to find any in-process modifications, as well as scan the names of running programs and windows.

This goes right along with my research on the subject - Before TBC I was a fairly aggressive botter, I have mentioned here before that I botted a priest from 1-60 and to fully exalted with Alterac Valley, I've pulled more stonescale eels from the ocean than a major fishing barge could... And I did it all without getting nailed.... of course I only did it while I was at the keyboard.

The funny thing there is that my played character has been reported for botting 3 times that I know of, writing UI mods while picking Whipper Roots or in Alterac Valley since you need a raid seems to raise some flags.

The links on warden are appreciated, Everything I saw showed that an active scan of all processes was run when launcher fired off, and other than looking at the process list WoW seems to stay in it's own space. Since Keyclone doesn't MODIFY anything in process, it shouldn't be a problem. Then again, playing WoW on linux shouldn't be a problem either Link.

I'd highly recommend you guys get off the warden topic. While I understand there's some concern for a common multiboxing program here, discussing how to get around warden and its methods of detecting cheats are gray area and something that "official sources" would probably frown upon. Also, the keyclone author has said he's looking into it. Leave it at that.

Quote:

---

Originally Posted by zanthor

I've run process monitors and debug tools to watch what is scanned on my system when I run wow, if I run Launcher.exe, it scans my process list, if I run WoW.exe, nothing scans my process list...

Of course this WAS pre-2.0, however I'd say that blizzard's patcher seeking out my wow.exe shortcuts and changing their target to Launcher.exe probably backs that up a little...

If I'm wrong, correct me, no need to be an ass.

---

The Launcher searches the active processes for known keyloggers. Starting WoW directly doesn't perform this check. Warden is completely separate.

Quote:

---

Originally Posted by Evilseed

Keyclone might become automatically bannable by Blizzard's Warden client.

---

This is BS. There is nothing like "auto"-banning. Blizz takes banning serious and will ALWAYS review the account before banning.

And to all the other people: COME ON!! Here is one guy, craving for attention and you all react to it!

My friend at Blizzard said, dont believe anyone who claims to have a friend at Blizzard. And youre damn right, thats a paradoxon.
Cheers.

Wow, this thread is filled with nothing but miconceptions and FUD. The only person who was remotely close was Wilbur.

Warden is a very intrusive program. On top of doing memory checks in process, it also actively scans out of process for known "bad software" via hashes. The links to Lax's blog is the only reading I would recommend to anyone.

Other miconceptions/FUD clarification:
-Blizzards bannings for 3rd party software are automated, it is when you bitch about your ban that they get human review, or if you get reported and they monitor you (because they don't detect what you are doing with method 1)
-Warden runs scans throughout your whole wow session.
-Warden scans out of process as much as it does in
-Techniques to "defeat" warden are just as wilbur stated, which is more of "faking results". If your client doesn't report warden scan data to their servers you get disconnected.
-Attempts to "defeat" warden are no futile. It is entirely possible if you know wtf you are doing.
-Lax said Greg hollunds book was laughable. (Maybe not exact quote, I think he mentioned it in his blog).
-The only truely successful person at doing so is Lax.
-Yes, call me a fanboi, because I am. Throughout the whole history of warden, there have only been 2 months (scattered about) of detectablility for the isxwow extension using his anti-detection measures.

Here is a closing factual statement: There are only a small handfull of people around here that will every be at or around 0% risk of getting banned. Those people are the ones who employ 100% hardware methods. Anything else is "technically" against the EULA/TOS. Synergy, multibox, keyclone, ahk.... you name it. What the software is used for is irrelevant, it is simply up to blizzards team for what they decide is bannable.

There is a risk using any software here, so if you don't want to get banned, the best option is to take 0% risk. Blizzard will notify you via e-mail letting you know that software you have is bannable, and it will come with either a 72 suspension or a full ban. But it won't say "software x is bad", it will say "you have something to make us do this, so figure out what it is on your own and remove it".

Overrall, the basic goal is to provide a nice medium between risk/reward. Multibox and other apps like it provide a very nice way of controlling multiple characters for minimal risk. With keyclone, it might be a very small amount more (currently). This is the happy medium that a lot of us go with, because we simply can't or don't want to dump extra money into hardware to mitigate the risk..

From all my currently knowledge on the subject I would say that the OP isn't presenting anything of merit. I would also agree with the person who said that AHK and/or AutoIT are more likely targets before something small like keyclone. There are bigger fish to fry, which is why blizzard has a lawsuit with MDY and has scans in place for their app, and not keyclone. It is not worth their time to persue....currently.

-S