Hi,
I remember that I have the same problem.
Microsoft Operating Systems manage badly subdirectories that are
deeper than 8. So Anti-viruses treated that as a virus action.
The same thing for tar files as anti-viruses can access to compressed
files (without passwords).
Regards,
Toufik
On Tue,
February 7, 20117:52 AM Hello: I downloaded your program a few months ago and
I love it. I am still learning how to use it fully. However, recentlyI had
cause to wonder about it I have Avira Antivirus. I also have XP Professional
and Netzero. A few days ago, I had looked at a video about
Off hand, this is just as likely to be a problem with the virus software
simply failing on a valid file. My recommendation is that you take the
file in question and upload it to an online virus scanning site... I
have not tested or used any of them in a while, but, here are two
possibilities
To Whom It May Concern,
I recently downloaded your open office version 3.2. Ever since that
download, I have gotten a blue screen warning me that a software issue has
caused Windows to stop my computer. This is the first time I have ever used
your product and I REALLY enjoy it. Any
Cool :)
I guess you should visit the OOo Security Project, and subscribe to that
mailing list:
http://security.openoffice.org
Malte.
Ravipriya Thushara wrote, On 10/21/09 06:26:
Hi,
Im developing a File format fuzzer for Open Office.org. So It'll be easier
to find vulnerabilities
using it.
Hi all,
Are there any known security flaws in the latest openoffice version that has
been disclosed?
I only seem to be able to find bulletin page for the vulnerabilites fixes for
all the different versions. If anyone feels uncomfortable revealing this
information even though it's
Hello!
I have a file Easterly.odt. I have used save/as with password to protect
it. However, I am not sure how secure it is when opened in
OpenOfficeWriter.I assume that it is in memory when editing. Can you
please advise. This file is the text of a book that I am writing. I am
also running
Peter Eberlein wrote:
Hi Mathias,
Mathias Bauer schrieb:
Peter Eberlein wrote:
Macro security is about macro execution, not about availability of the
BasicIDE.
And that's the point. You cannot forbid the execution of internal
non-document-bound macros with the security settings.
Peter Eberlein wrote:
Hi,
we want to restrict the use of the Basic IDE, but because of a missing
error handling in OpenOffice's macros, it is simple to produce an error
and to access the IDE (e.g. bind the macro
Depot.Depot.AddShortCuttoControl() to a field, a frame, a graphic).
The
Hi Mathias,
Mathias Bauer schrieb:
Peter Eberlein wrote:
Macro security is about macro execution, not about availability of the
BasicIDE.
And that's the point. You cannot forbid the execution of internal
non-document-bound macros with the security settings.
Regards
Peter
10 matches
Mail list logo