"Spyware" dll in P99's patch files.

[Chortles Snortles]

guys where did i agree to cheat and get permabanned
(lol)

[Tann]

Originally Posted by Chortles Snortles [You must be logged in to view images. Log in or Register.]

guys where did i agree to cheat and get permabanned
(lol)

Didn't you read the ToS?

[You must be logged in to view images. Log in or Register.]

[onions]

I have the utmost respect and gratitude for the folks keeping this game running.

There are some privacy concerns that keep me from playing until I buy a dedicated laptop as covid changed up my work. I'm sure i'm not alone in these concerns, as a lot of the playerbase is older and likely more employed than other games out there [You must be logged in to view images. Log in or Register.].

I do wish we had a better sense of what's at stake, privacy-wise. Not because I dont trust the staff, but because I know security breaches happen.

That all being said, it is what it is and I know i'll be playing again soon. Thanks again p99 people

[cd288]

Here are some old quotes on the DLL file.

Rogean (apparently - a commenter from a 2015 thread said this was a post from him): "As far as what it does.. I can tell you for a fact it does not collect information about processes unless they directly access Everquest memory space."

Deurbael (retired P99 GM - comment from 2014): "dsetup.dll doesn't modify any of your files, doesn't let us read your files, doesn't destroy your registry. It doesn't give us any kind of hands on access to your computer. It's there to detect cheats like Macroquest and ShowEQ so that we can have a truly hack free server. As a poster explained above, it is likely that someone submitted it to a (crappy, lazy) virus database and they filed it in the "well it does something but we can't be arsed to figure out what" section of their DB. So now it's going to flag on certain virus scanners."


Now - is this all true? Who knows. To some degree we'll just have to trust the staff unless someone with a lot of technical knowledge can break down the DLL and confirm what it has access to.