ISXWarden Release Thread - 2008-07-19 - ISXDK 30

[lax]

WARNING! WARNING! WARNING!
Terror level RED. ISXWarden download removed until problem is solved.

Last bans: 2008-07-28












WARNING! WARNING! WARNING!
Terror level RED. ISXWarden download removed until problem is solved.

Last bans: 2008-07-28

























Please do not post on the release thread, instead post in the WoW::General forum

What is ISXWarden?
ISXWarden protects against Blizzard's Warden for World of Warcraft. In a nutshell, this extension prevents Warden from disclosing any potentially harmful information about your system, at least against in-process modifications and hacks that use the Inner Space memory service (anything that ISXWoW or other IS extensions do will be protected, as long as they use the IS API to do the memory modifications). In other words, if you use Syndrome or other apps to hack WoW, those hacks are not protected. ISXWarden does not provide any additional out-of-process protection over the Inner Space stealth system, which simply protects Inner Space itself.

ISXWarden automatically loads and unloads ISXWoW when appropriate.

What can we expect on patch days?
ISXWarden is patch-specific. You will need to wait for it to be updated to work with the current version of World of Warcraft when it gets updated.

What can we expect on maintenance days?
Generally, not much.

What is WardenNet?
WardenNet is currently only used to check the version of ISXWarden. Signtaure tracking is no longer necessary, but may be re-enabled for informational purposes.

What is WardenLink?
WardenLink is a simple system enables external application developers to take advantage of ISXWarden's protection by requesting protection for DLLs, processes or windows, and can also make and remove memory modifications through ISXWarden. WardenLink must be explicitly enabled by entering the command "WardenLink" after loading ISXWarden (in World of Warcraft via the Inner Space console), after which the WardenLink-enabled applications may be launched.

How to use ISXWarden to protect other programs
In addition to WardenLink, which can be used by external programs to make memory modifications and request various protections, a LavishScript API is available to request protection for DLLs, processes or windows. This API can be used without the assistance of a developer, and can protect any program that does not make memory modifications to the WoW process (if that program does make in-process memory modifications, it can NOT be protected by this system).

All protection requests are case insensitive, so "FOO" is the same as "foo", and are substring searches, so "FOO" will cover "foo", "food", "banfoo", "foobar" and anything else containing FOO. Be careful not to protect things that should actually be there and are known to exist, such as kernel32.dll, wow.exe, and so on.

To protect a window (or group of windows by the same name) type this in the in-game IS console:

[lax]

[lax]

New and improved, now with WardenNet!

[lax]

Download the one for the ISXDK your version of IS uses. If you're using stable IS, you need the one that says "For ISXDK 27".

[lax]

ISXWarden updated today for WoW 1.10, would have been yesterday if the servers were up!

[lax]

Quote:

ISXWarden for WoW 1.10.1, I cant see the yellow or teal message about the variation.WardenNet indicate it is safe with the green message. Confused

Warden is currently inactive. If the only indication you see is "Dummy Warden loaded (no scan)" and nothing like "Normal Warden - auto - loaded (scan enabled and safe)", then there simply is no Warden to check the version of.

[lax]

jp608 wrote:

strange thing is, last week we got 1.10 in europe and yesterday we had extended maintenance due to a large patch. (in europe wednesday=patchday). so i assumed that we are running 1.10.1 now, however my "ext isxwarden" generates a message saying my isxwarden version mismatches my WoW version. When i go back to isxwarden for version 1.10 everything works fine. ( blue message saying my warden is 12 days old and it's safe to go). So im a bit confused if Europe is running 1.10 now or 1.10.1

In the future please do not post on the release thread, instead post in the WoW::General forum.

To answer this question, your WoW version is shown in the lower left corner when you launch the game. For US users it's 1.10.1, and from what I hear, EU are indeed still on 1.10

[lax]

ISXWarden build 20060415 fixes a non-critical bug -- ISXWarden would not re-load ISXWoW if Warden is disabled and you log out, then back in. It will now re-load ISXWoW The bug can be worked around with older ISXWarden versions by simply unloading and re-loading ISXWarden, or by manually loading ISXWoW. As this is not a critical fix, this update is only available for ISXDK 29, which is in use in Inner Space 1.06, currently under development.

[lax]

ISXWarden build 20060422 updates the algorithm used to find the signature of the loaded Warden. This will result in new signatures being found as if Warden were just updated.

[lax]

ISXWarden build 20060516 is a mandatory update, which also enforces a requirement of Inner Space build 3984 or higher. Inner Space builds 3984 and up have optional stealth instead of requiring stealth by default. ISXWarden enables the Inner Space stealth when loaded. Stealth must be enabled before logging into World of Warcraft to enable ISXWarden (you may load ISXWarden before login, or any time after stealth is enabled).

If you are worried about Warden, but want to use Inner Space for legitimate purposes, do not enable Stealth and do not use ISXWarden. Blizzard was able to detect that a stealth system affecting Warden existed in Inner Space build 3982 itself (note: they did not detect ISXWarden or ISXWoW, this detection was independent of anything like that). As a short-term, immediate solution I updated Inner Space so that the stealth system is not presently detected.

Longer-term solutions are under development.

[lax]

ISXWarden build 20060523 is a mandatory update.

This new version of ISXWarden employs high levels of protection, and has a few new features to boot.

* WardenNet is (possibly temporarily) not used for signature tracking in this version of ISXWarden. But, it does still check for ISXWarden updates for you when ISXWarden gets loaded.
* ISXWarden will stop the process from continuing if Warden exhibits unexpected behavior (e.g. in the event of a new version of Warden).
* ISXWarden will print a notification to the console if an application (exe, DLL, or window) is "hit" by Warden scans. Some apps are not protected by Warden, so these will show (Not Stealthed) in red. Apps that are protected will show (Stealthed) in green. I am debating whether to have ISXWarden submit this information to WardenNet to keep a database of things that Warden scans for, or just letting people share the information with each other.

[lax]

ISXWarden 20060524 is a non-mandatory update that fixes the "unexpected behavior #20" message for some people.

[lax]

ISXWarden-20060526 is a non-mandatory update that activates the new WardenLink system. WardenLink is now explained in the initial post on this thread.

[lax]

ISXWarden 2006-06-20 updates the extension for WoW 1.11.0

As of this update, Warden is not yet enabled after the patch. When it becomes enabled, ISXWarden will start spewing out error messages and drop you from the game, and there will be lots of posts on these forums asking what's going on and why ISXWarden is broken. All that will have happened is Warden will be enabled, and this will require another ISXWarden update. Let me know as soon as possible when Warden happens, but please refrain from making 600 posts unless it's to flame all the people who skip reading this and post asking why it's giving an error.

[lax]

ISXWarden 2006-06-21 fixes a crash bug in the 1.11.0-updated ISXWarden.

Warden has been re-enabled as of this posting, and everything appears normal (unchanged) and functional.