Dustin <
bughunte...@gmail.com> wrote in
news:XnsA02DAB0828FC7HHI2948AJD832@no:
>
> I'm not sure I'd credit him as the author... Possible, but not
> entirely likely. The slow infector relies on it not being detected for
> sometime, so that it can slowly work it's way into your backup
> history. As it's unknown at that point, it's a safe bet he'd include
> it in a supposedly "clean" image-short of install from clean media on
> known clean HD and no 3rd party apps. In reality this wouldn't work
> anymore due to the rapid rate in which samples are passed around and
> new definitions are posted to deal with them.
You can be certain the plan is my own. I've never seen anyone detail
such a plan as I've developed. I'm not saying it's complex, as if you
think it through with determined purpose, I suppose anyone could come up
with the same plan. Can that plan be improved...I haven't see how. Have
I seen anyone anywhere present such a plan....NO!
>
> In the past tho, the slow infector did have these backup systems in
> mind and intended to take advantage of the process.
The plan never uses any data that has been on a computer in use for any
amount of time. Could something go wrong...of course though unlikely if
the process is properly disciplined, but if such is discovered, there is
a failsafe backup plan for that. I've spent many hours testing than
thinking the plan through and it is as good as possible,
>
>> It does seem like a lot of work doing that when images are not the
>> right tool to battle malware. For the type of disaster recovery
>> images *do* address - there's no need to avoid slipstreaming.
>
> Agreed.
Wrong.
>
>> And, it doesn't help matters when Bear keeps presenting it as such.
>
> Based on his posts recently, he seems to behold some sort of grudge
> against techie types. Perhaps he feels they rip people off. He feels
> his plan puts techies out of business.
>
Not at all. It's the teach a person to fish thingy. My plan can be
easily enacted by anyone with the skills to download and install a
program. If they use it, they become self-reliant and have no need to
seek anyones help, lose no data ever, and can be certain they are using
a clean machine. Most end-users don't have the skills to become self-
reliant without such a plan. I also think the plan is worthy for
experienced users, as it eliminates the hours required to skillfully
clean a machine and be CERTAIN it is clean, not just have faith it is.
Such a concept is how I finally developed the plan as it is now. I
believe anything can be improved, and as I am the only contributor to
the plan at this point, experienced folks may be able to offer
suggestions on how to improve it if possible. I've had none of that,
from anyone here...just bitching.