Dustin <
calling.my.stalke...@huh.com> wrote in
news:XnsA156E6824FCD6B7Z317AGDTEHHI8AJ283@no:
> Bear <
bearbo...@gmai.com> wrote in
>
news:XnsA156AE0F254A5be...@130.225.254.104:
>
>> Dustin <
calling.my.stalke...@huh.com> wrote in
>> news:XnsA156B47395F1AB7Z317AGDTEHHI8AJ283@no:
>>
>>> Well, the only way the test would be fair then Bear is if we both
>>> use the same tools. right? So, there would be no clean image
>>> available to you for restoration. As that would be cheating.
>>> Wouldn't exactly be fair for me to have to hunt and fix things and
>>> you just blow a good image back onto the machine. I wasn't making a
>>> time to do this comparison here. :)
>>
>> Thank you Dustin. You helped prove that Imaging is the first and
>> formost thing a person should do before going out into the wild. If
>> you are not prepared, you are/may be fucked...and have to pay a
>> reterd, as opposed to retard, to get you outta the mess when ya
>> coulda done it yourself - free - and much much faster.
>
> I think you missed what I wrote completely here. Imaging is useful for
> hardware failures primarily, or I suppose, really seriously borked
> software/OS installations. It's not and never has been a cure for
> malware tho. The image isn't going to correct the problem which
> allowed the malware to get on the machine in the first place.
I don't think anyone missed my point. I certainly didn't miss yours. You
act as if there is a reliable way to prevent malware compromises. There
is not. Correcting the problem which allowed the malware to get on the
machine is impossible. What you mean by saying that, is stupid end-
users, or putting better prevention tools on board, or hardening your
system etc. Even after the best attempts at doing so, it is never bullet
proof.
>
> Proper security/firewall configuration is more important before going
> online than imaging the machine. You can image it when your happy its
> working as it should.
That is just wrong Dustin...back-asswards. Never image a system that has
been used in the wild except under very controlled circumstances such as
MS and program updates or installs. Installs can be a problem if they
are not from well known sources - but my plan includes a factory with MS
and Vendor Updates image in the event you discover you've installed
malware ridden programs. Test these programs well on your old system
before you reload your last known clean image to make updates on and
then reimage.
>
> Images can also fail, and restore discs sometimes don't even work from
> factory due to unforeseen bugs because they did not test them. The
> restore partition on an HP 9260f for example will not actually restore
> the system without a patch from HP being downloaded and installed
> first. If you try, you're told the restore discs you made are not for
> this computer.
Now you are reaching. Even with machines that come with system factory
images on the hard drive are unreliable besides usually very outdated.
Make your own when you first purchase a machine, or if you didn't do so,
restage and start over and make your image. Never rely on factory
restoration software that resides on your hard drive, or even factory
restoration discs. Make and update your own system images.
I always get factory restoration media (usually CD/DVDs) when I purchase
a machine as a last ditch standby. If they don't work, order some more.
CD/DVD's can be very unreliable and I do not recommend long term
reliance on them. I do recommend at least two external hard drives as
they can fail, and at least a third Cloud backup system. Triple
redundancy. Sounds a bit complicated for some folks, but most of that
can be automated and the rest takes seconds to initiate or setup. It is
very easy for end-users once shown how to do it, or for those who take
the time to learn it.
>
> As long as things like that crop up, and computers continue to break
> down; like it or not, people like me, are still useful to others. We
> can fix their problems and we don't rip them off, despite your
> unfounded claims that we do.
You don't teach them to fish though do you. You fix their machine, take
their money and tell them not to be so stupid next time - bye bye.
>
> I guess if anything, I've only proven that you are selective in what
> you read/respond to and take things out of context to try and prove
> your side of the argument.
You haven't proven shit Dustin.
>
>> Game, set, match :)
>
> Well, as I've always said, Umm.. no, I don't think so. In your dreams
> only, Bear.
>
Game, set, match.