[Next Message in Time] |
[Previous Message in Time] |
[Next Message in Topic] |
[Previous Message in Topic]
Message ID: 17450
Date: Thu Apr 6 23:58:25 BST 2000
Author: Lyrnia Jongleur
Subject: RE: [eqbards] I'm back ;)
> 1) It's pretty clear that we all don't want Verant (or anyoneSmedly is probably correct. The VAST majority of EQ players are kids. At
> else) snooping
> around in such things as Internet directories et al. If I recall
> correctly - the impression that this was being done - was from a
> post from a
> Necro board of a log of program that claimed they were reading this. Has
> anyone here verified this?
>
> Smedly claimed that this was false...
> 2) Smedly claimed all they did (and I thought Kevin CrawfordI have a problem with any of my data being "sampled" by a 3rd party whom I
> verified this)
> is that they run a Win32API call to see what active process were
> and what's
> in memory.
>
> If this is all Verant is doing - I'm not so sure I have a problem
> with this.
> I don't want them reading my hard drive - there is a chance for
> proprietary
> info. Hypothetically there's a chance that (say you had a word processor
> doc running) that proprietary info is in memory - but that's kind of a
> stretch. Plus - if you were really concerned about it - you
> should just be
> careful to shut everything down before starting EQ (I do this anyway to
> conserve memory).
>
> I'm curious what others think about this. Again - no scanning of file -
> simply checking memory and active processes.
> What's kind of silly about this - is how hard is it to change the name ofYep, easily
> the program? Couldn't you even code the program to generate a random
> process name everytime you ran?
> And isn't there a REALLY simple solution to thsi? Couldn't Verant encryptThey shouldn't be sending the data back. That's illegal and even Violates
> their packets? Perhaps this additional overhead would negatively impact
> performance - but I'd think if they are clever enough they could come up
> with something that would make it really hard for these programs.
> Especially since they could subtly change the algorhtym ever time they
> patch..