think
-mouser
To get mad about a single key in the registry, or a DLL file that is part of the installer and does nothing but suggest another program you can opt-in to install, is really misplaced concern in my view. All this hand wringing is best saved for *real* adware, spyware, hidden installs, etc. Stuff that really *does* install programs behind the scenes that users don't want.
-mouser
Josh that's incorrect, a DLL sitting there not in use is completely benign. It's only if it is loaded into a process can it cause harm, and even then no more harm than that process itself could do. It getting loaded into some processes address space cannot happen spontaneously, something must load it and that something is then the malicious application, not the DLL.
Sorry to be blunt but you're concerns here are unfounded.
-Eóin
What if someone else exploits it? I think some of you are very smart but naive people.
On the otherhand all I have seen so far either OC had a bug in the installer or it was an honest mistake on the developer`s side or it was some other problems that was causing OC`s unattended invisible installations. Just more excuses for more malign behaviours. You know if noone ever raised anything about these issues, you bet they would not be called bugs or honest mistakes.
Mouser, I am already trying to reach the developers who embedded this OC stuff in their apps. So It is not like I am coming and just bithcing about the same issues over and over again. I hope that more users talk to developers. As someone pointed out the Miro forum, you can see that Miro users are very unsatisfied with Miro`s desicion and I myself bitched about it in ther beta forums as well. They seemed like they had no idea what OC was up to.