hysgrubl <beast@remotecave.wilderness> Thou rude mechanicals. Thou
ineffective, fly-eating conspirator. Thou beggar. Four of thy five wits
went halting off, and now is the whole man governed with one. Ye
maundered and ye lectured:

> Kadaitcha Man wrote this:
>
>> mar0 <mar0@cox.net> Thou idiotic notable strumpet. Thou unsightly rag
>> of honour. Thou shag-haired crafty kern. Thou peevish baggage. Ye
>> squealed and ye spewed:
>>
>>> Hello,
>>>
>>> I have recently decided to take on the project of writing a utility
>>> that deceives spyware and websites that obtain and sell private
>>> information. I've written the preliminary outline for the code
>>> (sketched out the object classes for C# code) but I still have a lot
>>> of questions about its central mechanisms. Please respond if you can
>>> help.
>>> The first mechanism is rather simple - the utility will write fake
>>> cookies so that websites will obtain misinformation about what
>>> website was viewed previously. I'm using Firefox source to learn
>>> about how browsers store and organize cookies.
>>>
>>> The second mechanism is tougher - it will require sending
>>> misinformation about personal data to potential spyware processes
>>> (fake addresses, etc). For this, I will need to look at source code
>>> for spyware, or at least get a specific idea of what spyware looks
>>> for. So if you have source code or reverse-engineered code for known
>>> spyware processes, please send them to me.
>>>
>>> The third mechanism is the toughest - I am trying to learn how
>>> consumer database information (like http://www.studentlist.com) is
>>> stored so that misinformation can be sent to those databases as
>>> well. I imagine that most of these databases are sent information
>>> from people who use more invasive procedures (like the ones listed
>>> above), but if you know of any ways that these companies obtain and
>>> store data automatically, I would love to know about it.
>>>
>>> Thank you.
>>
>> The simpler solution to the whole problem is not to set out to
>> "decieve" the target of your deception, but to foil the target's
>> attempts to get the information in the first place. This has all been
>> done before, by many anti-malware applications, reputable ones at
>> that, not ill- and insanely-conceived new ones like yours. Much
>> foiling can also be achieved by using a simple .hosts file; again,
>> all done before, and all freely available.
>
> Option 1: Make your comp think your own machine is the site. Put
> this in the hosts file...
>
> 127.0.0.1 www.somenetwork.somedomain
>
> ...and then make sure your system is configured to resolve names there
> BEFORE it tries DNS (this is the default on Windoze and most *nix
> systems). Your system will never successfully contact that site
> again.
>
>
> Option 2: An HTML filter. Examples: Privoxy. Proxomitron.
> Configure them to erase or rewrite references to the site you wish to
> block.

You brain-dead ****slop gobbler.

--
alt.usenet.kooks - Pierre Salinger Memorial Hook, Line & Sinker:
September 2005, April 2006, January 2007.

Vescere puter subgalia meis.

"Now I know what it is. Now I know what it means when an
alt.usenet.kook x-post shows up."
AOK in news:ermdlu$nli$1@registered.motzarella.org