Libreoffice contains a number of harmless files used for testing purposes. However, on Microsoft Windows system, these files can trigger false positive alerts on various anti-virus software, such as Microsoft Security Essentials. For example, the alerts can be triggered when scanning the Red Hat Enterprise Linux 6 ISO file.
Libreoffice contains a number of harmless files used for testing purposes but these files trigger various AV software such as "Microsoft Security Essentials" with serious warnings. This means that anyone scanning our source ISO with these tools will receive false positive virus alerts.
Upstream received lots of comments about this and decided to alter the files so they were not longer triggers; see
We should do the same for the next ASYNC libreoffice or RHEL6.4 whichever is earliest.
(In reply to comment #0)
> Upstream received lots of comments about this and decided to alter the files
> so they were not longer triggers; see
A better link to a complete commit including decoding code:
doable, seeing as did it upstream already
FWIW what we'd have to do (assuming that we're not going to rebase in 6.4 to a later version, which I think is a given for the moment) is to backport my decrypt-on-the-fly-during-tests code and then unpack the sources, crypt the offending docs, and repack the sources in order to not have the raw files in the .src.rpms
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.