sivran
Long Live The Suite
Premium
join:2003-09-15
Arlington, TX
clubs:
 ·RoadRunner Cable
| reply to Bobby_Peru
Re: Targeting "Greyware" - Criteria & Definitions
I think I'll propose an amendment to Bobby Peru's example myself.
quote:
4) Fails to itself contain upon initial installation, and retain until complete uninstallation, and provide ALL of the following methods of quick, easy (define?) complete uninstallation, each of which singularly must completely Uninstall the software and any other software that said software imported...., including ??? , and which must not Uninstall, or in any way damage any other software, data, O/S and/or...? of the machine:
This is fine, if you're looking at it like this: "Application A, which is supported by Adware B, must remove Adware B and all components thereof upon being uninstalled."
But, if you look at it from the other direction: "Adware B, must upon being uninstalled..." Must Adware B prompt the user with, "Hey, you, uninstalling me will break Application A. Do you wish to uninstall that as well?" However, Adware B may not be smart enough to enumerate the different applications using it, or it may remember only the last application to use it.
There should also be an entry that explicitly addresses such programs, like certain P2P apps, that install separate adware/spyware components. Such applications should be required to provide uninstallers for these *ahem* "other" components, regardless of whether doing so would break the application or not. The uninstaller would of course warn the user of this, I'm sure. 
quote:
2) Questionable Installation exploit section ---
"Uses any sort of deceit, including, but not limited to, misleading statements (in EULAs or otherwise), false statements, or omissions, to manipulate the user into installing the software."
--
TCPA - Treacherous Computing
Kerio 2.1.5 - Best damn firewall
Home licensing should be just that. |
