Why not more safety measure in IS?

[Pitor]

I DON'T know what Warden detected this time or the last times.
I just say what I think.

Wouldn't IS be safer if it used rootkit, random named/folders/process and much more.
I don't want to bring down IS but Glider did kinda well with those things.
I get the feeling that IS relie on ISXWarden 110% and ignore everythng else. What IF ISXWarden fail. Would probably be harder to detect IS if it used rootkit and stuff?

What do you think?

[fearless]

http://en.wikipedia.org/wiki/Rootkit

You may want to read up on what a root kit can do before you ask somebody to put it on your computer.

[Pitor]

http://en.wikipedia.org/wiki/Rootkit

You may want to read up on what a root kit can do before you ask somebody to put it on your computer.

"A rootkit's only purpose is to hide files, network connections, memory addresses, or registry entries from other programs"
Sounds good, did I miss something?

If you rather want a ban than a rootkit then go ahead.

[fearless]

Sounds good, did I miss something?

Yes, the entire next paragraph.

A rootkit is often used to hide utilities. These are often used to abuse a compromised system,and often include so-called "backdoors" to help the attacker subsequently access the system more easily. For example, the rootkit may hide an application that spawns a shell when the attacker connects to a particular network port on the system. Kernel rootkits may include similar functionality. A backdoor may also allow processes started by a non-privileged user to execute functions normally reserved for the superuser. All sorts of other tools useful for abuse can be hidden using rootkits. This includes tools for further attacks against computer systems which the compromised system communicates with, such as sniffers and keyloggers. A possible abuse is to use a compromised computer as a staging ground for further abuse (see zombie computer). This is often done to make the abuse appear to originate from the compromised system or network instead of the attacker. Tools for this can include denial-of-service attack tools, tools to relay chat sessions, and e-mail spam attacks. A major use for rootkits is allowing the programmer of the rootkit to see and access user names and log-in information for sites that require them. The programmer of the rootkit can store unique sets of log-in information from many different computers. This makes the rootkits extremely hazardous, as it allows trojans to access this personal information while the rootkit covers it up.

Can a rootkit be used for good? Sure, but I think you are crazy if you want a rootkit of any sort installed on your computer. Glider uses rootkits? What happens if the dev for Glider says, "Gee, I could make 10k a day by using my subscribers as spam relays! Hah! they would never know!"

Rootkits are not the answer, or at least not an answer anybody should trust.

[Pitor]

Sounds good, did I miss something?

Yes, the entire next paragraph.

A rootkit is often used to hide utilities. These are often used to abuse a compromised system,and often include so-called "backdoors" to help the attacker subsequently access the system more easily. For example, the rootkit may hide an application that spawns a shell when the attacker connects to a particular network port on the system. Kernel rootkits may include similar functionality. A backdoor may also allow processes started by a non-privileged user to execute functions normally reserved for the superuser. All sorts of other tools useful for abuse can be hidden using rootkits. This includes tools for further attacks against computer systems which the compromised system communicates with, such as sniffers and keyloggers. A possible abuse is to use a compromised computer as a staging ground for further abuse (see zombie computer). This is often done to make the abuse appear to originate from the compromised system or network instead of the attacker. Tools for this can include denial-of-service attack tools, tools to relay chat sessions, and e-mail spam attacks. A major use for rootkits is allowing the programmer of the rootkit to see and access user names and log-in information for sites that require them. The programmer of the rootkit can store unique sets of log-in information from many different computers. This makes the rootkits extremely hazardous, as it allows trojans to access this personal information while the rootkit covers it up.

Can a rootkit be used for good? Sure, but I think you are crazy if you want a rootkit of any sort installed on your computer. Glider uses rootkits? What happens if the dev for Glider says, "Gee, I could make 10k a day by using my subscribers as spam relays! Hah! they would never know!"

Rootkits are not the answer, or at least not an answer anybody should trust.

They the glider people are fucked, but that has nothing to do with this. Lax can put virus into IS now without rootkit.
Can we keep it on topic?

[fearless]

I am keeping it on topic. You asked for a rootkit to be installed on your computer, mentioning that glider "did kinda well with those things" and I am responding. A rootkit in any form on your computer is a BAD idea.

ISXWarden is currently configured to disconnect your session if it sees any Warden activity it is unfamiliar with. Is this the best solution possible? I don't know, but it is far better then volunteering for getting a root kit.

[caytchen]

WoW will all time be userspace only. Using a driver to hide and protect InnerSpace opens up much more possibilites.

Your favourite antivirus programm probably uses kernel drivers aswell. Just because it has a rootkit-like functionality doesn't mean it is one

[Lax]

Sorry, but I do not intend to reduce your system stability by producing my own kernel-level code at this time. Any flaw in kernel code can produce a BSOD. The added safety by using a rootkit is next to nothing for something like Inner Space as well.

Inner Space may indeed move various things to the kernel level at some point, but don't hold your breath. It would not be in development in the next several months.

Regardless, I also don't need random people saying I should implement something just because they read about it on the internet and it sounded cool. I would leave the business before forcing a rootkit upon all of my customers, just to "help protect" my World of Warcraft customers. Please leave such discussions to the experts (if an expert wanted to chat with me about things, said expert could do so himself).

[eqjoe]

Besides, rootkits will not protect you from Blizzards detection. InnerSpace uses "intrusive" techniques that enable functionality that is not available with any other method.

If you want a far less stable and functional solution that installs a rootkit on your system, use Glider. But before you do, check out the Glider support forums.

-j