Hi Glenn, > > a) inject malign searches into /searches or /localsearches > > How difficult/easy is it to write malicious searches?
As easy, and with as far-reaching consquences as browser hacks for IE4, I guess. Since all we've done is turn off all the security mumbo-jumbo that breaks DQSD, that security is no longer in place for the user. I could think up a search that: - Registers itself to run at DQSD startup - Uses XmlHttp to download a binary from a remote server - WScript.Exec's that binary to open a port, and make the machine remote controllable So as long as the user can be convinced to add the search to their search dirs, this is doable. And if the evil-doer finds a way to silently inject evil.xml into /searches, nobody will even notice. I think this is a pretty far-fetched scenario at the moment, since our user base isn't huge (827 downloads of 3.1.9.1), but it's definitely something to look out for, that's why I'm worried. - Kim ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Archive: https://lists.sourceforge.net/lists/listinfo/dqsd-devel
