tag:blogger.com,1999:blog-3647430684627927763.post6168055812429100254..comments2008-01-17T12:39:35.244-05:00Scott J. Robertshttp://www.blogger.com/profile/02657251441213846202noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-3647430684627927763.post-77632220822240017012008-01-17T12:39:35.244-05:002008-01-17T12:39:35.244-05:00The exploit should also do the following:<BR/><BR/>-Have each dropped exploit coded just slightly different to keep signature-writers (AV, IDS, et al) on their toes<BR/>-decentralize C&C, leverage fast-flux and encrypt comms with a simple (fast) algorithm<BR/><BR/>Name it BitStorm. ;)Michaelhttp://www.blogger.com/profile/15879934504315589742noreply@blogger.comtag:blogger.com,1999:blog-3647430684627927763.post-45525187619325325432008-01-17T11:06:37.532-05:002008-01-17T11:06:37.532-05:00Interesting idea, but I'm guessing it would be hard to create something that would work on all the clients on all the platforms.<BR/><BR/>For example, a protocol specific attack may or may not work on Azureus which is written in Java and thus runs on a VM which handles memory and resource management very differently than a native app running without a VM.<BR/><BR/>Also I suggest selling this idea individually to RIAA, MPAA and whatever AA is there for software to maximize profits. lol<BR/><BR/>Also, charge a license fee per every affected machine, and if they don't pay up sue them for infringement. ;)Lukehttp://www.blogger.com/profile/01547722716619591211noreply@blogger.com