full-disclosure - Rootkit For Spyware? Hide your adware from

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

From: James.Cupps at sappi.com (James.Cupps@...pi.com)
Subject: Rootkit For Spyware? Hide your adware from

True, points taken.

 

James Cupps
Information Security Officer



-----Original Message-----
From: Harlan Carvey [mailto:keydet89@...oo.com] 
Sent: Thursday, September 23, 2004 9:38 AM
To: full-disclosure@...ts.netsys.com
Cc: Cupps, James; avalon@...ro.anu.edu.au
Subject: RE: [Full-Disclosure] Rootkit For Spyware? Hide your adware from

 

 

> It depends on which kit they based it on. My guess
> is these guys weren't
> good enough to do the coding themselves so they
> stole someone else's code.

That, or they're learning (rootkit coding training via
Blackhat), or they're simply purchasing it (there are
folks who do custom rootkit coding for hire).

> Of course I can' t think of any rootkits under any
> kind of license so I
> guess it isn't really stealing. Maybe the kits'
> authors should track these
> bozo's down and ask for some compensation. They are
> probably good enough to find them.

I don't see a correlation between coding and tracking
someone down.  Also, as stated, there are some who are
already writing rootkits for pay.

This message may contain information which is private, privileged or
confidential and is intended solely for the use of the individual or entity
named in the message. If you are not the intended recipient of this message,
please notify the sender thereof and destroy / delete the message. Neither
the sender nor Sappi Limited (including its subsidiaries and associated
companies) shall incur any liability resulting directly or indirectly from
accessing any of the attached files which may contain a virus or the like. 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20040923/9f52b9cf/attachment.html