Privacy and Multiuser Systems
The second main complaint Ive seen is that GDS searches the entire local system, including the files for all users, not just the current user or the one who installed. Theres something to this, in that it means that one must use GDS with special careif at allon systems with multiple users. The documentation makes clear that GDS is intended for a single user machine, or at least that it can only be installed on a single users login for a particular computer. Exactly how it functions on a multiuser system depends on how that system is configured and who the user is who installed GDS. But its already been pointed out by others that since GDS indexes the entire computer, it will index the private files of other users on the system. You may, therefore, view files belonging to other users. If they use Web mail, you may be able to view their mail.Lets think this through. GDS will only install on a system when the user doing the installing is an administrator, and it will only run when the user who installed it is logged in. I tested this myself. So, in order for you to be able to view the files and browser caches of other users on the system, you must be the system administrator. Guess what, Sherlock! You already had access to those files! Shocking as it may be, GDS only makes it easier to do what you already had explicit power to do. This objection is speciousness defined. If you still dont like the prospect of the system administrator having access to such information, you can mitigate it somewhat by modifying GDS options to have it not index https pages, which will eliminate most Web mail. You also can configure Internet Explorer to delete all temporary files when it quits. Next page: Platform and browser restrictions.