BKCMVRDM.RVW 20041010

"Computer Viruses for Dummies", Peter Gregory, 2004, 0-7645-7418-3,
U$14.99/C$21.99/UK#9.99
%A Peter Gregory peter.gregory@hartgregorygroup.com
%C 5353 Dundas Street West, 4th Floor, Etobicoke, ON M9B 6H8
%D 2004
%G 0-7645-7418-3
%I John Wiley & Sons, Inc.
%O U$14.99/C$21.99/UK#9.99 416-236-4433 fax: 416-236-4448
%O http://www.amazon.com/exec/obidos/AS...bsladesinterne
http://www.amazon.co.uk/exec/obidos/...bsladesinte-21
%O http://www.amazon.ca/exec/obidos/ASI...bsladesin03-20
%P 274 p.
%T "Computer Viruses for Dummies"

This book isn't really about computer viruses. The introduction
contains an awkwardly worded paragraph in Gregory refuses to define
computer viruses, but makes it clear that he intends, in common with
Humpty-Dumpty, to use the term "virus" in whichever way he chooses.
Mostly he chooses to use it to mean "lots of things that can be
annoying to your computing, including malware, spam, and other
circumstances." To the non-specialist this might seem to be an
advantage. After all, who cares what you call the problem as long as
you're protected from it? Unfortunately, the different types of Bad
Things out there work in different ways. So why tell the reader to
use a firewall, and avoid getting their addresses on spam lists, when
neither technology has anything to do with protecting you against
viruses?

Part one is supposed to allow you to evaluate your virus situation.
Chapter one, which purports to give you the information necessary to
understand virus risks, contains a lot of generally irrelevant
material, such as the various versions of Windows. (It is ironic that
the most meager entry given is that for Windows XP, since XP was
actually an important increase in virus risk. The internal structure
of the operating system makes it harder to clean and protect--DCOM is
more difficult to shut off, and System Restore makes it harder to get
rid of risky utilities--and the increased wealth of hiding places
makes disinfection much more problematic.) The symptoms listed in
chapter two are not reliable indicators of the presence; or absence;
of a virus. The section that repeats much of the content of chapter
one is peculiar. The book is intended for, err ..., average to novice
computer users, so having a chapter telling you how to find out if
your computer actually has antiviral software already installed is
possibly a good thing. But chapter three spends an awful lot of time
telling you things about icons, and not as much time on how you might
determine the version or signature update status.

Part two is concerned with actually protecting yourself. Chapter four
suggests a reasonable process for installing new antiviral software
once you have it. First, however, there is some questionable advice
in regard to choosing said software. "Reputable" is not an easily
quantifiable term: the ordinary user is going to have a hard time
distinguishing between "is highly functional" and "costs a lot and has
the biggest, brightest boxes and ads." In addition, Gregory strongly
promotes the idea of bundled packages, without noting that such
applications seldom have the "best of breed" in all categories, or
that a failure in one component can often turn off the whole suite.
Again, since this book is aimed at the typical user, chapter five's
review of configuration options is not altogether useful: it does not
always point out the dangers of certain actions. Chapter six, on
scanning your computer and email, has very little helpful material.
Dealing with infections, in chapter seven, is somewhat better. The
content regarding interpretation of warning messages is worthwhile.
But the terse accounts of modifying the Registry and restoring or re-
installing files may lead readers into difficulty.

Part three deals with maintenance of protection. Chapter eight,
regarding updating of signatures, does not seem to have much value,
and nine, on patching, really only has a couple of useful pages, and
those only for Windows and Office. Firewalls and anti-spyware
programs are important, but chapter ten fails to note how much you
need to know about network traffic in order to effectively use a
firewall, and that anti-spyware scanners don't detect viruses and vice
versa. Some reasonable guidance on protecting your PDA (Personal
Digital Assistant) is given in chapter eleven. Chapter twelve
suggests making backups of your data, and has a few other points that
might make you a bit safer. (I'd propose that telling people not to
open attachments and avoid P2P/file sharing systems would result in
better safety.)

Part four is supposed to tell us more about what viruses are. Chapter
thirteen is a not-terribly-reliable history. (BRAIN was not the
first, Concept was not a polymorph [and came later, anyway], and
during the heyday of BBSes the dominant viruses were boot sector
infectors--which couldn't be spread by BBSes. Also, it is highly
ironic that Gregory seems to imply that the Norton product was the
first antivirus--since Peter Norton spent over year telling people
that viruses were a myth and computer users should not foolishly give
their money to those antivirus-product-selling scammers.) (I agree
with Gregory on the virus writers, though.) Other types of malware
and scams are briefly discussed in chapter fourteen. Chapter fifteen
has a little (and old) information on virus operations, and some other
miscellaneous stuff.

Part five is the usual "Part of Tens," this time giving us nine myths
and an actual situation (there are *way* more than ten myths), and
minimal information about ten antivirals.

This book is addressed to people who aren't interested in viruses, and
wouldn't want to read a book about viruses. (Which makes for an
interesting marketing challenge.) It is difficult to say that nobody
would ever benefit from reading this text. But it is much harder to
envisage a situation in which this circumscribed data would save the
day, and really easy to imagine situations in which the little
information in this tome could be a very dangerous thing.

copyright Robert M. Slade, 2004 BKCMVRDM.RVW 20041010

--
======================
rslade@vcn.bc.ca slade@victoria.tc.ca rslade@sun.soci.niu.edu
============= for back issues:
[Base URL] site http://victoria.tc.ca/techrev/
or mirror http://sun.soci.niu.edu/~rslade/
CISSP refs: [Base URL]mnbksccd.htm
Security Dict.: [Base URL]secgloss.htm
Book reviews: [Base URL]mnbk.htm
Review mailing list: send mail to techbooks-subscribe@egroups.com
or techbooks-subscribe@topica.com

Rob Slade, doting grandpa of Ryan and Trevor wrote:

SPAMMER! DIE!!!!

Michael J. Pelletier wrote:

Usually, when one posts a reply to a spammer, he trims the spam.

--
-bts
-This space intentionally left blank.

"Michael J. Pelletier" <mjpelletier@mjpelletier.com> wrote in message news:dMHwd.46097$ka2.6508@fed1read04...

1) Learn what spam is.
2) Reserve your outbursts for where they are pertinent.

Rob Slade is very welcome to post reviews of on topic material, and that material was on topic for
all of the groups he posted to.

In article <dMHwd.46097$ka2.6508@fed1read04>, Michael J. Pelletier wrote:
Do you have any thoughts on what should happen to morons who quote 100+ lines
just to add one stupid line?

--
--Tim Smith

Michael J. Pelletier wrote:

Please go and buy a copy of "usenet for dummies".

Yep. These "make a buck" guys have run the Computer
Book industry out of business. The "Computers" shelf
at Walden Books is gone ... and good riddance. I must
have bought 100 or so, and I really don't remember a
single one of them that got it right. I had 10 - 15 C books
trying to learn C-programming back in the early 90s,
and by the time I did, C++ was the new rave, so I
started over with 10 - 15 more books, until OOP took
over, and then I tried to learn Microsoft OPP ( oops! )
where I could write AutoCAD in 5 minutes, but
could not add 2 + 2. I finally gave up, and started
dating girls .. marriedkidsdivorcedmarriedgrandkids ..
must have learned something, but I sure don't know how.

johns

On Tue, 21 Dec 2004 04:06:56 -0800, "johns"
<johns123xxx@xxxmoscow.com> wrote:

C language = Programming language developed in 1972.
C++ language= Originally called C with classes. Developed also in the
AT&T Co.'s Bell Laboratories in the early 1980s.

Twenty years later?


Geo

Tim Smith wrote:

First, sorry to interrupt your attention spam for so long. Second, stop
being a dork.

Tim Smith wrote:


Or how about idiots that comment for nothing? You obviously have other
issues...

In article <yB8yd.69520$ka2.36170@fed1read04>, Michael J. Pelletier wrote:
You are the one who quoted 100+ lines just to add a stupid one line (and not
even appropriate--book reviews are not spam) comment, and are now taking two
separate posts to reply to that criticism.

It's amusing how you newbies to usenet think that just because you managed
to find newsreader software, you don't need to learn anything about proper
netiquette.

--
--Tim Smith

"Tim Smith" <reply_in_group@mouse-potato.com> wrote in message
news:%gnzd.9833$9j5.320@newsread3.news.pas.earthli nk.net...
I agree completely with Tim both times.

You were a moron (Tim's words) to quote that whole book review just in order
to post 1 completely wrong line, flaming the author (Who did a very good
job). Take a quick tip and don't flame unless you know what you are talking
about.

Also, why did you take 2 irrelevant posts to reply to Tim's (admittedly
flamming, but you started it) comment. To me that takes a complete moron.

Adrian.

----------

Easy way to tell a n00b from a l33t:
A noob will try to put everyone else down, even the leets, for doing
anything.
A leet will help others regardless of what they are doing or how wrong it
is.

Personally, I do not think book reviews should be posted to this news group.
If someone wants to do this on their web site find. However, it is not
needed here........if it looks, smells like SPAM it probably is.

Adrian Pavone wrote:

Michael J. Pelletier wrote:
Not only a clueless luser, but a top-posting clueless luser...

Go look in a Usenet archive, Rob has been posting these reviews for
quiet a while now, probably longer than you've had access to a computer.

In fact, I went off and had a google, and he's been posting reviews
using the sprint.ca address since mid-1999, and the earliest book review
I can find by a "Rob Slade" is dated Mar 25 1997.

And, like many others, I find them useful.

Cheers,
Gary B-)

Gary R. Schmidt wrote:

You sound more and more like an jackass...and a bottom feeding on at that...

"Gary R. Schmidt" <grschmidt@acm.org> writes:

.... who doesn't even know that his articles have a b0rken header.
But that's fine with me - his articles never made it to the spool of
my news server.

You may want to read
From: roberts[]mukluk.hq.decus.ca (Rob Slade, the doting grandpa of Ryan Hoff)
Newsgroups: alt.books.technical,biz.books.technical,misc.books .technical
Subject: Book review index
Date: 3 Aug 1995 14:31:14 -0500
Organization: UTexas Mail-to-News Gateway
Lines: 1541
Message-ID: <00994533.768051A0.6441@mukluk.hq.decus.ca>
which lists some 600 reviews. And I didn't need no Google for that.

Of course.
--
The first entry of Sin into the mind occurs when, out of cowardice or
conformity or vanity, the Real is replaced by a comforting lie.
-- Integritas, Consonantia, Claritas

Adrian Pavone wrote:

I am amazed at what an ass you are...

"XRay" <XRay@nospam.net> wrote in message news:egUFd.142$Nu.9@fed1read04...
I'm amazed that you quoted me in order to complain about Tim's post.

Adrian

Michael J. Pelletier <mjpelletier@mjpelletier.com> wrote:
Define "this".

Define "here".

And the word you are looking for is "spam", not "SPAM" (Yes, the
(non-)capitalization makes a big difference.). And no, it isn't "spam"
either. A single unique posting can never be spam. It can be *unwanted*,
*off-topic*, etc., but it isn't / can't_be "spam".

"Frank Slootweg" <this@ddress.is.invalid> wrote in message
news:41e94b9b$0$78203$1b2cd167@news.wanadoo.nl...
Lol, I agree that it isn't spam, but you do know that Michael would just
come back with the fact that there are a number of reviews here (all on
topic though).

Thanks for correcting him on the SPAM postings . Didn't even occur to me
to.

Adrian