Skip to Content
6-08-2010 @ 12:54PM
"If they can prove you had to violate a copyright to get it into your RAM, or that the act of executing it from RAM was copyright infringement"That's not the issue exactly. It's if blizzard owns the memory space that is being used, is the issue. Glider would look into the active memory space that WoW is using. By "hijacking" the memory space or by launching the WoW client within the Gliders own memory space it could examine the unencrypted data. This process was made famous (he did not invent it) by the guy that made the Diablo Trainers back when Diablo 1 was the big kid on the block. He went by the name "enigma" ( if I remember correctly ). enigma's software invaded the memory space then read the decrypted data and modified it on the fly. This type of invasive software was one of the reasons ( one of many ) MS moved to the isolated memory style we have now ( and was already in the server software of the time ). So the big question ( at least for software developers like me ) is if the company that owns the software and licenses it for use, owns the memory space it is using at run time. There was a lot of noise about this early on, but seems to have been swept under the rug. I realize this might not seem like a huge issue but looking at it from the idea that it becomes legal for software makers to examine what you are looking a, when they feel like it, sort of bothers me. what will keep them from embedding code to allow remote viewing of your current work? I can see the responses now, "your not important enough to watch", which is mostly true. That's not the point. The point becomes, do you own what you are working on if the EULA ( which no one reads ) stats that they can examine your work and take ownership if they desire? Or can they sue for royalties when their software is used in the creation of a product. I also realize most companies will not go this route but if the possibility is there then someone will use it. It seems to be human nature.
First time? A confirmation email will be sent to you after submitting.
Members enter your username and password.
Enter your AOL or AIM screenname and password.
Please keep your comments relevant to this blog entry. Email addresses are never displayed, but they are required to confirm your comments.
When you enter your name and email address, you'll be sent a link to confirm your comment, and a password. To leave another comment, just use that password.
To create a live link, simply type the URL (including http://) or email address and we will make it a live link for you. You can put up to 3 URLs in your comments. Line breaks and paragraphs are automatically converted — no need to use <p> or <br /> tags.