Pueblo Native wrote:
M Henri Day wrote:
«... *Is it time to now introduce such measures to the OpenOffice.org
Core
to greatly reduce any future risk from scripted infections?*»
Good question....
Henri
We need to maintain the most important security factor in any system:
the one between the keyboard and the chair. Don't open strange
documents, don't blindly click on links in e-mails, and don't turn the
responsibility of common sense over to your CPU.
I fully agree with you here but we still have to minimize the threat.
How about making the macro code prevent the creation of executable files
in the first place. Don't allow it to change the file to executable and
even change the file to a read/write file by default. If you need the
file to be executable, you have to do it manually. This is the first
line of defense.
The person sitting in the chair needs to be educated. Vista is making
the educated person feel like and idiot (according to the people that I
have talked to) by their access control feature. Many just switch it
off because it is a pain.
If OOo is going to keep promoting security features, then the features
will have to be better than what the competition offers.
I like the fact that I cannot turn off the macro warning in OOo 2.2. I
would like the feature to have a WWW link to an explanation of the
warning or a more info button.
--
Due to the move to M$ Exchange Server,
anything that is a priority, please phone.
Robin Laing
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
