<?xml version="1.0" encoding="UTF-8"?>

<rss version="2.0" xmlns:blogChannel="http://backend.userland.com/blogChannelModule">

<channel>
<title>Re: Targeting &#x22;Greyware&#x22; - Criteria &#x26; Definitions in Security</title>
<link>http://www.dslreports.com/forum/r12746533</link>
<description></description>
<language>en</language>
<pubDate>Wed, 02 Dec 2009 10:56:20 EDT</pubDate>
<lastBuildDate>Wed, 02 Dec 2009 10:56:20 EDT</lastBuildDate>

<item>
<title>Re: Targeting &#x22;Greyware&#x22; - Criteria &#x26; Definitions</title>
<link>http://www.dslreports.com/forum/remark,12765300</link>
<description><![CDATA[<A HREF="/useremail/u/887018"><b>Vvian Kalyss</b></A> : Good points, all.<br><br>We could just call it a "software removal tool", plain and simple. If they ask why their software is on that list, say by vote and request of many users. There, now they can't complain about people calling them malware or whatever.<br><SMALL>--<br>Mikami Vvian, resident Girlfriend of Steel, care of the Tokyo-3 Middle Daughters Club</SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,12765300</guid>
<pubDate>Fri, 25 Feb 2005 03:59:28 EDT</pubDate>
</item>

<item>
<title>Re: Targeting &#x22;Greyware&#x22; - Criteria &#x26; Definitions</title>
<link>http://www.dslreports.com/forum/remark,12765127</link>
<description><![CDATA[<A HREF="/useremail/u/874811"><b>sivran</b></A> :  <BLOCKQUOTE><SMALL>quote:</SMALL><HR>The ONLY TAC should be, does this software produce from time to time AD's that some users may not want.<HR></BLOCKQUOTE><br><br>You're making the same mistake that Eric called me on earlier, Z: trying to develop solely functional criteria. You're going to catch far too much benign software with just this one test. For instance, web browsers display ads that some users may not want. While these ads may not be part of the browser itself--except in the case of Opera--your criteria doesn't distinguish this fact. It met your criteria and therefore, must be detected. You should look at the La-La land thread, particularly starting at this post: &raquo;<A HREF="/forum/remark,12665642~mode=flat~days=9999~start=620#12751476">ASW Vendors in La-La Land</A><br><br>And now I'm going to try to tackle Bobby Peru's criteria in their entirety, because it's interesting and easier than coming up with something myself, and may aid me in coming up with something myself in any case. ;)<br><br> <BLOCKQUOTE><SMALL>quote:</SMALL><HR>1) USER DESIRE<br>Unwanted by any user for any reason, at any time, as determined by ...<HR></BLOCKQUOTE><br><br>"As determined by the user looking for an uninstaller," perhaps? ;)<br><br> <BLOCKQUOTE><SMALL>quote:</SMALL><HR>2) QUESTIONABLE INSTALLATION EXPLOITATION --- Failure to provide for express user consent to Installation, with prior presentation of clear, concise, easy to understand Notice as specified below. Use 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.<HR></BLOCKQUOTE><br><br>I have yet more to add here: "The fact that a user agreed to an EULA shall under no circumstances revoke their right to remove the software covered by that EULA, nor shall this alone constitute consent, especially if the EULA in question contains any of the aforementioned characteristics."<br><br> <BLOCKQUOTE><SMALL>quote:</SMALL><HR>3) AD PRESENTATION<br>Displays and/or plays advertisements (?define display, plays and advertisements?).<HR></BLOCKQUOTE><br><br>This one is tricky to write, without catching such things as web browsers, email clients, and even usenet readers. I'm not sure I can actually do this. "Displays, from time to time, some potentially undesired advertisements in any form, excepting the following: advertisements contained in a webpage that the user elected to view (to exclude web browsers from detection), and advertisements contained in email or usenet postings (to exclude email clients and usenet readers). These exceptions shall not apply to advertisements which are "built-in" with the program itself, e.g. Opera's free version. Thus, Opera, while a web browser, is still "adware" by this definition, as is Eudora. Running a program does not constitute electing to view a website, thus if running some software results in a webpage being opened which contains advertisements, that software shall be deemed to display advertisements, regardless of whether or not any are "built-in" to the program itself."<br><br> <BLOCKQUOTE><SMALL>quote:</SMALL><HR>4) Uninstall<br>At initial installation, and at all times subsequent to that, up until complete removal, 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:<br><br>A) Windows Programs Add/Remove<br><br>AND<br><br>B) Windows--> Start--> Programs<HR></BLOCKQUOTE><br><br>easy (define?) -> "Easy shall be defined as following standard, intuitive methods of uninstallation, such as via the program's entry on the start menu, and the Windows Add/Remove programs tool."<br><br>software imported...., including ??? , and which must not Uninstall, or in any way damage any other software -> "including any and all updates, extensions, modifications, and companion and/or dependent programs, e.g., removing "WildTangent WebDriver" must remove any and all WildTangent software. The uninstaller must prompt the user with this information, clearly explaining why additional software is being removed, and offer them the chance to cancel the operation should they so desire. Failure in this or any of the aforementioned aspects will result in detection.<br><br> <BLOCKQUOTE><SMALL>quote:</SMALL><HR>5) INFORMATION and COMMUNICATION<br>Monitors and/or collects, and/or detects, and/or stores, and/or transmits any information related to the use of the machine, and/or any application, and/or any user of the machine, and/or any user's use of the machine, and/or any connection, unless... (Experts must help out here to craft language to narrowly include normal o/s and application functioning, yet exclude the scumware. I know this is a tough one, but I think it can be done).<HR></BLOCKQUOTE><br><br>Add a clause here about "for marketting, advertising, or any other commercial purposes."<br><br> <BLOCKQUOTE><SMALL>quote:</SMALL><HR>6) PURPORTED "EULA"/"LICENSE" SECTION #1<br>Contains any purported "EULA", "contract", "license", "agreement", "licensing agreement"...... that fails to provide:<br>a)<br>AND<br>b)<br><br>(specify presentation/display minimum characteristics: when displayed, how long it must be displayed, procedure required to "Agree", how it is displayed - Font size, color scheme, line spacing, where in "document" and where in "display" of document enumerated language must be display - first "page"..)<HR></BLOCKQUOTE><br><br>The EULA display must include copy and paste functionality, should the user wish to paste it into a text editor or word processor for closer review. EULAs should include, at the top, the phrases "This program displays advertisements" and/or "This program tracks usage for commercial purposes" as appropriate to the program's behavior. The EULA that is displayed to the user must be complete and unabridged. A web link does not constitute an EULA, nor shall a web link satisfy the issues of "user consent" or "user desire."<br><br> <BLOCKQUOTE><SMALL>quote:</SMALL><HR>7) PURPORTED "EULA"/"LICENSE" SECTION #2<br><br>Contains any purported "EULA", "contract", "license", "agreement", "licensing agreement"...... that states, implies and/or alleges in any manner:<br><br>a)<br>and/or<br>b)<HR></BLOCKQUOTE><br><br>That the user does not have the right to remove the software ;) <br><br> <BLOCKQUOTE><SMALL>quote:</SMALL><HR>8) MACHINE/APPLICATION/CONNECTION PERFORMANCE<br>Negatively impacts the performance, use, and enjoyment of a machine(specify a range of machine characteristics), as determined by the user and/or (specify expert(s), and/or groups).<HR></BLOCKQUOTE><br><br>This one is just too dicey. Many users cry loudly about how anti-virus and software firewalls bog their systems down, and this criteria would thus have to catch them all. Perhaps an exclusion could be added here, but what about malware posing as such? (eg, Veloz/eAcceleration)<br><br> <BLOCKQUOTE><SMALL>quote:</SMALL><HR>9) VISIBILITY/CONTROL/STARTUP<HR></BLOCKQUOTE><br><br>A program shall not hide from the user, or it will be detected.<br><br> <BLOCKQUOTE><SMALL>quote:</SMALL><HR>10) VENDOR CONTACT INFORMATION --<br>Fails to provide (specify how provide) ALL of the following information: Contact Info (specify: Complete physical address, phone, email, Registered Agent's contact info...)<HR></BLOCKQUOTE><br><br>No comments here...<br><SMALL>--<br><A HREF="http://www.againsttcpa.com/">TCPA </A>- Treacherous Computing<BR><A HREF="http://download.kerio.com/dwn/kpf/kerio-pf-2.1.5-en-win.exe">Kerio 2.1.5</A> - Best damn firewall<BR>Home licensing should be just that.</SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,12765127</guid>
<pubDate>Fri, 25 Feb 2005 02:45:01 EDT</pubDate>
</item>

<item>
<title>Re: Targeting &#x22;Greyware&#x22; - Criteria &#x26; Definitions</title>
<link>http://www.dslreports.com/forum/remark,12764644</link>
<description><![CDATA[<A HREF="/useremail/u/1058899"><b>LilBambi</b></A> : bump... too good a list of important links to let it slip too far down the listing.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,12764644</guid>
<pubDate>Fri, 25 Feb 2005 00:40:00 EDT</pubDate>
</item>

<item>
<title>Re: Targeting &#x22;Greyware&#x22; - Criteria &#x26; Definitions</title>
<link>http://www.dslreports.com/forum/remark,12753954</link>
<description><![CDATA[<A HREF="/useremail/u/1140294"><b>Blackbird</b></A> : <div class="bquote"><SMALL>said by  LilBambi <A HREF="/useremail/u/1058899"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A>:</SMALL><br><br>Maybe the only thing that is really needed here is a very simple law that makes EULAs null and void - if they work against the wishes of the user?<br> </DIV> I (not any software house) own my computer. I make the choice to install or remove whatever software I want, as long as fees, copyright, and intellectual property rights are respected. A EULA is a licensing agreement, not a statement of computer ownership. It is a statement of agreement of what the software may do while on my computer, and my acceptance of those terms. That does not give installed software any right, in perpetuity, to remain on my computer if I choose the license and software removed. There need be no finding of harm in the software, 'working against my wishes', or any other justification for my removing it. If I want it removed, I have that right, pure and simple. And I can use any tool appropriate to that removal task, either provided by the software maker, provided by a third party, or provided by myself (including file deletion or drive reformat). Downloaded software is a GUEST on our computers, perhaps paid for, perhaps free, but persisting there only at our pleasure.<br><I>Edit: spelling :( </I><br><SMALL>--<br>If God wanted us to work with electrons, He'd make them big enough to see...</SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,12753954</guid>
<pubDate>Wed, 23 Feb 2005 23:02:37 EDT</pubDate>
</item>

<item>
<title>Re: Targeting &#x22;Greyware&#x22; - Criteria &#x26; Definitions</title>
<link>http://www.dslreports.com/forum/remark,12751645</link>
<description><![CDATA[<A HREF="/useremail/u/1058899"><b>LilBambi</b></A> : Maybe the only thing that is really needed here is a very simple law that makes EULAs null and void - if they work against the wishes of the user? Some Software Lemon Law or something like that.<br><br>The user owns the equipment, nothing should be allowed there that the user doesn't want, right?<br><br>If an owner of equipment finds that the software doesn't stack up to expectations, or it has shown itself to have ill effects to the user or their equipment, or it doesn't play well with the users other software, the owner of the equipment should have the right to remove that software regardless of the EULA ... maybe under some Software Lemon Law?<br><br>Hmmm...might need some further thought and discussion.<br><br>Any thoughts on that?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,12751645</guid>
<pubDate>Wed, 23 Feb 2005 19:04:04 EDT</pubDate>
</item>

<item>
<title>Re: Targeting &#x22;Greyware&#x22; - Criteria &#x26; Definitions</title>
<link>http://www.dslreports.com/forum/remark,12749265</link>
<description><![CDATA[<A HREF="/useremail/u/889138"><b>ZOverLord</b></A> : When Microsoft embedded the <B>Pop Up Blocker</B> it never ASKED anyone if they were using it for AD's!<br><br>The ONLY TAC should be, does this software produce from time to time AD's that some users may not want.<br><br><B>Yes/No</B><br><br>Anything else, any more detailed of a TAC will only be a reason for LEGAL action, lawyers will PICK apart each other ITEM in the TAC and claim their clients software does NOT meet the criteria for that Item, and request <B>Millions of Dollars</B> for the harm caused!<br><br>Geeze, if a woman can sue over spilling Hot Coffee on her lap because the lid on the cup did not say <B>CONTENTS is HOT</B> what do you think ANY detailed TAC will save you from.<br><br><B> The SOLUTION to this problem is LESS DETAIL not MORE DETAIL, MORE DETAIL GETS YOU IN COURT!</B><br><br>Allow the user to un-check <B>Just as MICROSOFT does in the POP-UP BLOCKER!</B><br><br>My God, these vendors are FALLING into the LEGAL TRAP! that these CRAPWARE vendors want.<br><br>We are not talking about MAPPING the Human Gene Pool here!]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,12749265</guid>
<pubDate>Wed, 23 Feb 2005 15:02:27 EDT</pubDate>
</item>

<item>
<title>Re: Targeting &#x22;Greyware&#x22; - Criteria &#x26; Definitions</title>
<link>http://www.dslreports.com/forum/remark,12749159</link>
<description><![CDATA[<A HREF="/useremail/u/874811"><b>sivran</b></A> : I think I'll propose an amendment to Bobby Peru's example myself. <br><br> <BLOCKQUOTE><SMALL>quote:</SMALL><HR>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:<HR></BLOCKQUOTE><br><br>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."<br><br>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. <br><br>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. ;) <br><br> <BLOCKQUOTE><SMALL>quote:</SMALL><HR>2) Questionable Installation exploit section ---<HR></BLOCKQUOTE><br><br>"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." <br><SMALL>--<br><A HREF="http://www.againsttcpa.com/">TCPA </A>- Treacherous Computing<BR><A HREF="http://download.kerio.com/dwn/kpf/kerio-pf-2.1.5-en-win.exe">Kerio 2.1.5</A> - Best damn firewall<BR>Home licensing should be just that.</SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,12749159</guid>
<pubDate>Wed, 23 Feb 2005 14:53:10 EDT</pubDate>
</item>

<item>
<title>Re: Targeting &#x22;Greyware&#x22; - Criteria &#x26; Definitions</title>
<link>http://www.dslreports.com/forum/remark,12749153</link>
<description><![CDATA[<A HREF="/useremail/u/879997"><b>dadkins</b></A> : Question, *IF* I agree to an EULA to install whatever, and said EULA(in legalese) states that I cannot "modify" or "change" _______ , and I decide to REMOVE this "item", is that not modifying/changing it? <br><br>Once I find that "it" is doing something that I do NOT agree with, I cannot REMOVE "it" with whatever tool I choose?<br><br>Is Add and Remove Programs next in these BS lawsuits? ProcessGuard/RegProtect/SpywareGuard/RegSeeker/etc. better look out as well, no? <br>Using regedit is against the law now?<br>Is this CRAPWARE lawsuit fiasco stupid or what?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,12749153</guid>
<pubDate>Wed, 23 Feb 2005 14:52:15 EDT</pubDate>
</item>

<item>
<title>Re: Targeting &#x22;Greyware&#x22; - Criteria &#x26; Definitions</title>
<link>http://www.dslreports.com/forum/remark,12749097</link>
<description><![CDATA[<A HREF="/useremail/u/658312"><b>danny9</b></A> : Eric, Thanks for your time and trouble in making us aware what's going on. Your efforts are appreciated and I have learned alot on the complexities of these issues of which I was never aware of before. Thanks again!:)<br><SMALL>--<br>To Think or not to Think: That is the real question. VoicePulse 07/29/04</SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,12749097</guid>
<pubDate>Wed, 23 Feb 2005 14:45:51 EDT</pubDate>
</item>

<item>
<title>Re: Targeting &#x22;Greyware&#x22; - Criteria &#x26; Definitions</title>
<link>http://www.dslreports.com/forum/remark,12749046</link>
<description><![CDATA[<A HREF="/useremail/u/795407"><b>SnowyOne</b></A> : To dispel any claims of an unfair selection system, with the exception of the browser/OS itself any program that connects to or makes use of computers www connection ought to be TAC'ed. That behavior alone should be worth some measure of points. So what if an AV updater scores a 1? A score of 1 is not cause for action. The programs that have their behavior manipulated to fall within an accepted TAC level with no meaningful change to their overall scheme (unwanted behavior) would have the additional challenge of the<br>initial TAC score, which would be fair because because it's applied to all programs that in any way make use of a www connection.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,12749046</guid>
<pubDate>Wed, 23 Feb 2005 14:39:14 EDT</pubDate>
</item>

<item>
<title>Re: Targeting &#x22;Greyware&#x22; - Criteria &#x26; Definitions</title>
<link>http://www.dslreports.com/forum/remark,12748635</link>
<description><![CDATA[<A HREF="/useremail/u/1140294"><b>Blackbird</b></A> : <div class="bquote"><SMALL>said by  Bobby_Peru <A HREF="/useremail/u/827318"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A>:</SMALL><br><br> 1) Unwanted by any user for any reason, as determined by ... </DIV>  I'd change this to: <B>1) Unwanted by any user for any reason <I> at any time </I>, as determined by ... </B><br>I think right up front has to be addressed (even indirectly) the issue that the user MAY have once accepted some kind of EULA or OK button, but now elects (legitimately) to revoke that choice. EULA acceptance appears to be the spearpoint of the malware litigation threats, so the concept needs to be established that anti-malware tools exist, in part, to assist a user <B> who has changed his mind </B> about any earlier EULA acceptance.<br><SMALL>--<br>If God wanted us to work with electrons, He'd make them big enough to see...</SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,12748635</guid>
<pubDate>Wed, 23 Feb 2005 13:54:26 EDT</pubDate>
</item>

<item>
<title>Re: Targeting &#x22;Greyware&#x22; - Criteria &#x26; Definitions</title>
<link>http://www.dslreports.com/forum/remark,12748239</link>
<description><![CDATA[<A HREF="/useremail/u/827318"><b>Bobby_Peru</b></A> : Eric, first thank you as always for finding/making the time to keep at this in general, and for your above gathering of definitions.<br><br>I can not read through them now, and could only spend a short time on this now, but for what little this may be worth, here's a frame work to perhaps get started.  Of course avoiding the "name calling" that these miscreants seem to bring out in me, would be highly recommended.  Huge holes exist at this point, but here goes...<br><br>------------------------------<br><br><B>Software Detection and Removal Tool Version 0.000.001--</B><br><br>Purpose:<br>This software attempts to detect other software that meet the enumerated criteria as listed below.  Software is selected for testing by many means, including user suggestions and submissions.  <br><br>Modification and Notice:<br>These criteria may be modified, altered, or otherwise changed, at any time, and with no notice.  <br><br>Should any modification be made, we will provide notice, but are under no obligation to do so, other than should such a modification result, or allow for software, or recent or new versions of software to no longer be detected (less detection), we warrant that we will give clear, unambiguous prior Notice to our customers, by prior posting of any such changes and their effects on our site, on the Update Page, the Download Page, and any other applicable pages, and by providing such notice through our software's Update procedure.<br><br>(Specific NOTICE details  stated- Font size, size of Notice pop-up if any, color scheme, minimum time pop-up must remain on screen, procedure required to close pop-up).<br><br>NOTE: DETECTION INDICATES ONLY MEETING ONE OR MORE OF THE BELOW CRITERIA.  USERS CHOOSE WHAT DETECTED SOFTWARE THEY WANT TO REMAIN ON _THEIR_ MACHINES, AND WHAT SOFTWARE THEY WILL REMOVE.  ANY SUGGESTIONS REPRESENT THE RESULTS OF OUR RESEARCH INTO USER'S OWN PREFERENCES, EXPERTS ADVICE, AS WELL AS OUR PREFERENCES.  USERS ARE UNDER NO OBLIGATION TO FOLLOW ANY SUGGESTIONS.<br><br> <B>--- CRITERIA FOR DETECTION AND USER SELECTABLE REMOVAL---</B><br><br>1) USER DESIRE<br>Unwanted by any user for any reason, at any time, as determined by ...<br><br>AND/OR<br><br>2) QUESTIONABLE INSTALLATION EXPLOITATION ---  Failure to provide for express user consent to Installation, with prior presentation of clear, <B>concise</B>, easy to understand Notice as specified below. Use 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.<br><br>AND/OR<br><br>3) AD PRESENTATION<br>Displays and/or plays advertisements (?define display, plays and advertisements?).<br><br>AND/OR<br><br>4) Uninstall<br>At initial installation, and at all times subsequent to that, up until complete removal, 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:<br><br>A) Windows Programs Add/Remove<br><br>AND<br><br>B) Windows--> Start--> Programs<br><br>5) INFORMATION and COMMUNICATION<br>Monitors and/or collects, and/or detects, and/or stores, and/or transmits any information related to the use of the machine, and/or any application, and/or any user of the machine, and/or any user's use of the machine, and/or any connection, unless... (Experts must help out here to craft language to narrowly include normal o/s and application functioning, yet exclude the scumware.  I know this is a tough one, but I think it can be done).<br><br>AND/OR<br><br>6) PURPORTED "EULA"/"LICENSE" SECTION #1<br>Contains any purported "EULA", "contract", "license", "agreement", "licensing agreement"...... that fails to provide:<br>a)<br>AND<br>b)<br><br>(specify presentation/display minimum characteristics: when displayed, how long it must be displayed, procedure required to "Agree", how it is displayed - Font size, color scheme, line spacing, where in "document" and where in "display" of document enumerated language must be display - first "page"..)<br><br>AND/OR<br><br>7) PURPORTED "EULA"/"LICENSE" SECTION #2<br><br>Contains any purported "EULA", "contract", "license", "agreement", "licensing agreement"...... that states, implies and/or alleges in any manner:<br><br>a)<br>and/or<br>b)<br><br>AND/OR<br><br>8) MACHINE/APPLICATION/CONNECTION PERFORMANCE<br>Negatively impacts the performance, use, and enjoyment of a machine(specify a range of machine characteristics), as determined by the user and/or (specify expert(s), and/or groups).<br><br>9) VISIBILITY/CONTROL/STARTUP<br><br>10) VENDOR CONTACT INFORMATION --<br>Fails to provide (specify how provide) ALL of the following information: Contact Info (specify: Complete physical address, phone, email, Registered Agent's contact info...)<br><br>.....<br><br>[Edit: 1st mark-up, now including <div class="bquote"><SMALL>said by Blackbird SR:</SMALL><BR><BR>1) Unwanted by any user for any reason at any time , as determined by ... </DIV> and <div class="bquote"><SMALL>said by sivran:</SMALL><BR><BR>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.</DIV>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,12748239</guid>
<pubDate>Wed, 23 Feb 2005 13:03:27 EDT</pubDate>
</item>

<item>
<title>Re: Targeting &#x22;Greyware&#x22; - Criteria &#x26; Definitions</title>
<link>http://www.dslreports.com/forum/remark,12746717</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : "It should be added that whenever there are doubts about the classification of software, the manufacturer of the software is contacted about any doubts.<br><br>Should the manufacturer decide to not answer such mails, the support forum is used to discuss the problem with the public."<br><br>Ref; &raquo;<A HREF="http://www.safer-networking.org/en/targetpolicy/" >www.safer-networking.org/en/targetpolicy/</A><br><br>Seems to me that anti-malware vendors are only subject to their users...not the ad boys. Also seems that user wishes should be as much a criteria as any definition.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,12746717</guid>
<pubDate>Wed, 23 Feb 2005 09:48:37 EDT</pubDate>
</item>

<item>
<title>Re: Targeting &#x22;Greyware&#x22; - Criteria &#x26; Definitions</title>
<link>http://www.dslreports.com/forum/remark,12746533</link>
<description><![CDATA[<A HREF="/useremail/u/1058899"><b>LilBambi</b></A> : Using the above listed info, I guess what we need is a:<br><br>Scumware Remover<br><br>The new Scumware Remover would give users the ability to remove any and all items that could be considered scumware. The program should, like MS AntiSpyware does, list the threat level for each program's group of installed 'stuff' including files, folders (hidden or not), registry entries, etc. Give an option to remove any 'unwanted' program.<br><br>Using COAST's definition.<br><br>Scumware <br>A slang term for spyware or any unwanted software/programs installed on your computer.<br><br>That should be able to include anything from A-Z and no one could say they were being targeted because it is a user's personal preference based on desire and threat level.<br><br>Eric great job of bringing all these together in one place.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,12746533</guid>
<pubDate>Wed, 23 Feb 2005 09:18:42 EDT</pubDate>
</item>

<item>
<title>Targeting &#x22;Greyware&#x22; - Criteria &#x26; Definitions</title>
<link>http://www.dslreports.com/forum/remark,12746264</link>
<description><![CDATA[<A HREF="/useremail/u/378696"><b>eburger68</b></A> : Hi All:<br><br>As we've seen from the initial responses to Lavasoft's new Threat Assessment chart, developing criteria for "anti-spyware" applications to target unwanted software can be a tricky, difficult business. To facilitate the discussion of these issues, I thought it might help to post a short list of existing targeting criteria being used by various anti-spyware companies as well definitions of "spyware," "adware," and related terms that exist on the Net.<br><br>Take a good, hard look. I think you'll find that almost all the criteria and definitions developed so far leave something to be desired. The term I've used for the title of this very thread (which I've borrowed from TrendMicro) conveys the difficulty of defining and naming the kinds of software that users want "anti-spyware" applications to detect and remove from their computers.<br><br>-----------------------------------------------<br>Adware/Spyware Targeting Criteria & Definitions<br>-----------------------------------------------<br><br>~~~~~~~~~~~~~~~~~~<br>Targeting Criteria<br>~~~~~~~~~~~~~~~~~~<br><br>Lavasoft - Threat Assessment Chart<br>&raquo;<A HREF="http://www.lavasoftnews.com/ms/tac_main.shtml" >www.lavasoftnews.com/ms/tac_main.shtml</A> (old)<br>&raquo;<A HREF="http://www.lavasoftnews.com/ms/research/tac.htm" >www.lavasoftnews.com/ms/research/tac.htm</A> (new)<br><br>Microsoft - Criteria for Listings <br>&raquo;<A HREF="http://www.spynet.com/info_spywarecriteria.aspx" >www.spynet.com/info_spywarecriteria.aspx</A><br><br>See also: Microsoft - Contact and Dispute Information for Vendors<br>&raquo;<A HREF="http://www.spynet.com/vendors.aspx" >www.spynet.com/vendors.aspx</A><br><br>Pest Patrol - Is it a Pest?<br>&raquo;<A HREF="http://research.pestpatrol.com/WhitePapers/ScoringCriteria.asp" >research.pestpatrol.com/WhitePap&middot;&middot;&middot;eria.asp</A><br><br>Spybot Search & Destroy - Target Policy<br>&raquo;<A HREF="http://www.safer-networking.org/en/targetpolicy/index.html" >www.safer-networking.org/en/targ&middot;&middot;&middot;dex.html</A><br><br>Sunbelt - Listing Criteria<br>&raquo;<A HREF="http://research.sunbelt-software.com/listing_criteria.cfm" >research.sunbelt-software.com/li&middot;&middot;&middot;eria.cfm</A><br><br>~~~~~~~~~~~<br>Definitions<br>~~~~~~~~~~~<br><br>Aluria - Adware on Your PC<br>&raquo;<A HREF="http://www.aluriasoftware.com/spywarelab/spywarelabdetails/71/" >www.aluriasoftware.com/spywarela&middot;&middot;&middot;ails/71/</A><br><br>Aluria - Forms of Spyware<br>&raquo;<A HREF="http://www.aluriasoftware.com/spywarelab/spywarelabdetails/46/" >www.aluriasoftware.com/spywarela&middot;&middot;&middot;ails/46/</A><br><br>Aluria - Spyware Overview<br>&raquo;<A HREF="http://www.aluriasoftware.com/spywarelab/spywarelabdetails/50/" >www.aluriasoftware.com/spywarela&middot;&middot;&middot;ails/50/</A><br><br>ARS Technica - Malware: what it is and how to prevent it<br>&raquo;<A HREF="http://arstechnica.com/articles/paedia/malware.ars" >arstechnica.com/articles/paedia/malware.ars</A><br><br>COAST Glossary<br>&raquo;<A HREF="http://www.coast-info.org/glossary.htm" >www.coast-info.org/glossary.htm</A><br><br>Computer Associates - Glossary<br>&raquo;<A HREF="http://www3.ca.com/securityadvisor/glossary.aspx" >www3.ca.com/securityadvisor/glossary.aspx</A><br><br>Computer Associates - What is Spyware?<br>&raquo;<A HREF="http://www3.ca.com/securityadvisor/newsinfo/collateral.aspx?cid=64232" >www3.ca.com/securityadvisor/news&middot;&middot;&middot;id=64232</A><br><br>doxdesk.com - Definitions of parasite-related terms<br>&raquo;<A HREF="http://www.doxdesk.com/parasite/definitions.html" >www.doxdesk.com/parasite/definitions.html</A><br><br>Eric L. Howes - Junkware: A New Name for Spyware<br>&raquo;<small>https</small>://<A HREF="https://netfiles.uiuc.edu/ehowes/www/junkware.htm">netfiles.uiuc.edu/ehowes/www/junkware.htm</A><br><br>Intermute - What is Spyware?<br>&raquo;<A HREF="http://www.intermute.com/spysubtract/researchcenter/index.html" >www.intermute.com/spysubtract/re&middot;&middot;&middot;dex.html</A><br><br>Pest Patrol - Glossary<br>&raquo;<A HREF="http://research.pestpatrol.com/WhitePapers/Glossary.asp" >research.pestpatrol.com/WhitePap&middot;&middot;&middot;sary.asp</A><br><br>PC Pitstop - What is Spyware?<br>&raquo;<A HREF="http://www.pcpitstop.com/spycheck/whatis.asp" >www.pcpitstop.com/spycheck/whatis.asp</A><br><br>SpyBuster -  What is Spyware and Adware?<br>&raquo;<A HREF="http://www.spy-buster.com/spywareinfo.htm" >www.spy-buster.com/spywareinfo.htm</A><br><br>Spywaredata.com - Definitions<br>&raquo;<A HREF="http://www.spywaredata.com/spyware/spyware-adware-definitions.php" >www.spywaredata.com/spyware/spyw&middot;&middot;&middot;ions.php</A><br><br>SpywareGuide.com - Categories<br>&raquo;<A HREF="http://www.spywareguide.com/category_list_full.php" >www.spywareguide.com/category_list_full.php</A><br><br>SpywareGuide.com - Intro to Spyware<br>&raquo;<A HREF="http://www.spywareguide.com/txt_intro.php" >www.spywareguide.com/txt_intro.php</A><br><br>SpywareInfo.com - What is Spyware?<br>&raquo;<A HREF="http://www.spywareinfo.com/articles/spyware/" >www.spywareinfo.com/articles/spyware/</A><br><br>SpywareWarrior.com - History of the Term Spyware<br>&raquo;<A HREF="http://spywarewarrior.com/viewtopic.php?t=10215" >spywarewarrior.com/viewtopic.php?t=10215</A><br><br>Symantec - Expanded Threats<br>&raquo;<A HREF="http://securityresponse.symantec.com/avcenter/expanded_threats/index.html" >securityresponse.symantec.com/av&middot;&middot;&middot;dex.html</A><br><br>TechTarget.com - Spyware<br>&raquo;<A HREF="http://searchcio.techtarget.com/sDefinition/0,,sid19_gci214518,00.html" >searchcio.techtarget.com/sDefini&middot;&middot;&middot;,00.html</A><br><br>Webopedia.com - Spyware<br>&raquo;<A HREF="http://www.webopedia.com/TERM/s/spyware.html" >www.webopedia.com/TERM/s/spyware.html</A><br><br>Webroot - spyware defined<br>&raquo;<A HREF="http://www.webroot.com/spywareinformation/spywaredefined/" >www.webroot.com/spywareinformati&middot;&middot;&middot;defined/</A><br><br>Webroot - spyware terminology & definitions<br>&raquo;<A HREF="http://www.webroot.com/spywareinformation/terminology/" >www.webroot.com/spywareinformati&middot;&middot;&middot;inology/</A><br><br>Webroot - what is adware?<br>&raquo;<A HREF="http://www.webroot.com/spywareinformation/spywareadware/" >www.webroot.com/spywareinformati&middot;&middot;&middot;eadware/</A><br><br>Wikipedia - Adware<br>&raquo;<A HREF="http://en.wikipedia.org/wiki/Adware" >en.wikipedia.org/wiki/Adware</A><br><br>Wikipedia - Spyware<br>&raquo;<A HREF="http://en.wikipedia.org/wiki/Spyware" >en.wikipedia.org/wiki/Spyware</A><br><br>Best,<br><br>Eric L. Howes]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,12746264</guid>
<pubDate>Wed, 23 Feb 2005 08:25:55 EDT</pubDate>
</item>

</channel>
</rss>
