Hi Bob:
I think you can take comfort from the following thoughts:
1) The macro virus protection will warn you if a document has ANY kind of
active content in it. If you do not trust the document or its source, you
simply say "Disable Macros" when prompted and you are utterly safe.
2) If you wish to disable all macros, do not install Visual Basic for
Applications. That's it: they're gone: the run-time engine is no longer on
your computer.
Personally, I wouldn't do that, because various things such as the Clip
Gallery which are part of Office depend on VBA for their functioning: some
of the Word user interface is done in VBA, some commands are also.
3) To cause any damage, a macro has to find out that it is on a Mac, find
out where the stuff that could be damaged is, then call Apple system
commands to do its nasty work. The techniques involved are not simple and
they're not at all common. It requires a level of technical expertise well
above the abilities of your average virus writer: most of the viruses out
there (despite what the media might have us believe...) are fairly
simplistic and rather badly programmed by people who usually do not have any
great skill at programming.
The likelihood that someone with the necessary skills to defeat the security
provisions of both Microsoft and Apple might spend the time it would take
with practically zero chance of success is small. To spread, a virus needs
to find a critical mass of computers it is compatible with in the network
population. Given that that probably means something like 25 per cent of
the network population, there's no chance of finding that many Macs out
there (a virus that does damage on Mac will not do so on Windows or
vice-versa...).
4) Microsoft is removing VBA, from all of its products. The reason is that
by its very design, it cannot be made sufficiently secure for a
massively-networked world such as we are now living in. It was designed to
be convenient and powerful when computers were stand-along (or networked
only within the company).
VBA has been replaced by something called The Common Language Runtime, which
is designed from the ground up to be secure. The most common example of it
is dot-Net, which is designed from a clean sheet of paper to survive in the
white-heat flames of the Internet
In the meantime, the flavour of VBA contained in Mac Word is very severely
cut back. Security wasn't the reason they did that: lack of time and money
was. But the effect is that a lot of the powerful system calls you need to
write a damaging virus are simply not available in the Mac Word flavour of
VBA (either Word X or Word 2004).
So if I were you, I would leave VBA in place (it is on my computer...) run
an AntiVirus (I use Norton...) and a firewall (I use BrickHouse...). Then
relax. Not enough of VBA works on the Mac to give you a serious likelihood
of getting a problem.
Hope this helps
This responds to article
from "Bob Harris" said:
Thanks for that. I might drop them a note, although surely you would expect
that it would have occurred to them previously that an easy way to prevent
macro viruses is to prevent macros. It would seem that, for whatever
reason, they feel like macros are far too valuable to let customers disable
them outright.
Thanks for your thoughts, and for the info,
Bob H
--
Please respond only to the newsgroup to preserve the thread.
John McGhie, Consultant Technical Writer,
McGhie Information Engineering Pty Ltd
Sydney, Australia. GMT + 10 Hrs
+61 4 1209 1410, mailto:
[email protected]