From: HeyBub on
"According to security vendor Prevx, the authors of the rootkit which was
the cause of a large number of unbootable systems which applied the MS10-015
patch issued last week have issued a patch to fix the incompatibility."

http://blogs.pcmag.com/securitywatch/2010/02/rootkit_authors_issue_patch_fo.php

All your roots belong to us...


From: Daave on
HeyBub wrote:
> "According to security vendor Prevx, the authors of the rootkit which
> was the cause of a large number of unbootable systems which applied
> the MS10-015 patch issued last week have issued a patch to fix the
> incompatibility."
> http://blogs.pcmag.com/securitywatch/2010/02/rootkit_authors_issue_patch_fo.php
>
> All your roots belong to us...

OK, so here's the plan.

I will shut off my firewall and disable my AV program. I will then
intentionally get infected with that particular rootkit. Then I will
download and install the patch that the authors of this rootkit issued
last week so that when I apply the MS10-015 patch, I won't get the BSOD.
Cool! No more incompatibility!


From: Jose on
On Feb 18, 11:59 am, "Daave" <da...(a)example.com> wrote:
> HeyBub wrote:
> > "According to security vendor Prevx, the authors of the rootkit which
> > was the cause of a large number of unbootable systems which applied
> > the MS10-015 patch issued last week have issued a patch to fix the
> > incompatibility."
> >http://blogs.pcmag.com/securitywatch/2010/02/rootkit_authors_issue_pa...
>
> > All your roots belong to us...
>
> OK, so here's the plan.
>
> I will shut off my firewall and disable my AV program. I will then
> intentionally get infected with that particular rootkit. Then I will
> download and install the patch that the authors of this rootkit issued
> last week so that when I apply the MS10-015 patch, I won't get the BSOD.
> Cool! No more incompatibility!

I want to do that too.

I think the the best way to understand these things is to experience
them for yourself and learn how to fix them.

Where do you go to get infected with that particular rootkit? I have
been trying for a week.
From: PA Bear [MS MVP] on
MSRC: Update - Restart Issues After Installing MS10-015 and the Alureon
Rootkit
http://blogs.technet.com/msrc/archive/2010/02/17/update-restart-issues-after-installing-ms10-015-and-the-alureon-rootkit.aspx

MMPC: Restart issues on an Alureon infected machine after MS10-015 is
applied
http://blogs.technet.com/mmpc/archive/2010/02/17/restart-issues-on-an-alureon-infected-machine-after-ms10-015-is-applied.aspx
--
~PA Bear


HeyBub wrote:
> "According to security vendor Prevx, the authors of the rootkit which was
> the cause of a large number of unbootable systems which applied the
> MS10-015
> patch issued last week have issued a patch to fix the incompatibility."
>
> http://blogs.pcmag.com/securitywatch/2010/02/rootkit_authors_issue_patch_fo.php
>
> All your roots belong to us...

From: Bob I on


Jose wrote:

> On Feb 18, 11:59 am, "Daave" <da...(a)example.com> wrote:
>
>>HeyBub wrote:
>>
>>>"According to security vendor Prevx, the authors of the rootkit which
>>>was the cause of a large number of unbootable systems which applied
>>>the MS10-015 patch issued last week have issued a patch to fix the
>>>incompatibility."
>>>http://blogs.pcmag.com/securitywatch/2010/02/rootkit_authors_issue_pa...
>>
>>>All your roots belong to us...
>>
>>OK, so here's the plan.
>>
>>I will shut off my firewall and disable my AV program. I will then
>>intentionally get infected with that particular rootkit. Then I will
>>download and install the patch that the authors of this rootkit issued
>>last week so that when I apply the MS10-015 patch, I won't get the BSOD.
>>Cool! No more incompatibility!
>
>
> I want to do that too.
>
> I think the the best way to understand these things is to experience
> them for yourself and learn how to fix them.
>
> Where do you go to get infected with that particular rootkit? I have
> been trying for a week.

Why not ask ol' ANGELKISSES420 ?

 |  Next  |  Last
Pages: 1 2 3
Prev: WinXP Driver Issue
Next: can't delete program