[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [suse-security] Intrusion spyware malware key stroke detection



I just furtively took a peak out the window.  No black helicopters.  No black 
SUVs.  No men in black suits.  No men in white suits either.  I'll keep 
checking. 
Even  paranoids  have   enemies. 
............................


On Wednesday 22 February 2006 09:10, Chris Quinn wrote:
> That's very odd.  Do your search queries frequently take you to the same
> web server?  If so, that server's logs will contain the search query you
> entered.
>
> There may be additional possibilities, but I can't think very clearly at
> the moment; the noise from all of the black helicopters makes it very
> difficult to concentrate.
>
> On Wednesday 22 February 2006 3:53 am, Martin wrote:
> > I use suse 9.3 pro on home network. Boxed retail DVD set.   Suse
> > firewall. Security updates are current.   KDE  Konqueror and / or
> > Firefox. Comcast cable internet service provider.   No alias.
> >
> >  Everyday I am seeing spam email which is a reflection of complex
> > sensitive key word phrases I had typed into google just  a few days
> > previously.
> >
> > What are the security implications of this?  How do I configure what I
> > have to stop this?  What additional measures might be appropriate?  Is
> > this spying for  commercial purposes or could it be US Government spying?
> >  The linux network worm?
> >
> > Aliasing?  Fire wall configuration?  Stop always connected cable internet
> > and go back to using on demand dialup.?
> >
> > My first reactions are to look into aliasing. Or go back to on demand
> > dialup.
> >
> > But if keystrokes are being detected then there is no security.  Very
> > alarming.
> >
> > Thanks to any who can help
> > Martin
>
> --
> Regards,
> Chris Quinn
> chris@xxxxxxxxxx
> ____________________
> http://blog.quinns.net

-- 
Check the headers for your unsubscription address
For additional commands, e-mail: suse-security-help@xxxxxxxx
Security-related bug reports go to security@xxxxxxx, not here