On Thu, March 31, 2016 7:56 pm, Paul Kosinski wrote:
> I disable Javascript in our PDF viewer. PostScript (which underlies
> PDF) is a Turing-complete executable language, and even has a mechanism
> to read and write files, so it could cause some trouble on its own.
Good idea!
For windows
I disable Javascript in our PDF viewer. PostScript (which underlies
PDF) is a Turing-complete executable language, and even has a mechanism
to read and write files, so it could cause some trouble on its own.
On Thu, 31 Mar 2016 10:36:18 -0500
Noel Jones wrote:
> Known
Thanks Noël.
On Thu, Mar 31, 2016 at 5:36 PM, Noel Jones wrote:
> Known malware will still be detected, even if you ignore the
> troublesome PUA sigs.
>
> These aren't really false positives since the .pdf really does
> contain javascript. So the sigs are working as
Known malware will still be detected, even if you ignore the
troublesome PUA sigs.
These aren't really false positives since the .pdf really does
contain javascript. So the sigs are working as intended.
The alternative is to communicate to your users that .pdf files
containing javascript are
That's known to me Steve.
I'm afraid malware will not be detected in that case.
P.
On Thu, Mar 31, 2016 at 3:43 PM, Steve Basford <
steveb_cla...@sanesecurity.com> wrote:
>
> On Thu, March 31, 2016 2:33 pm, polloxx wrote:
> > Since the new Clamav database we have a lot more false positives for
On Thu, March 31, 2016 2:33 pm, polloxx wrote:
> Since the new Clamav database we have a lot more false positives for
> PUA.Pdf.Trojan.EmbeddedJS-1 and PUA.Win.Trojan.EmbeddedPDF-1.
> What can we do about this, except disabling PUA?
Create a local.ign2 with the following lines:
Since the new Clamav database we have a lot more false positives for
PUA.Pdf.Trojan.EmbeddedJS-1 and PUA.Win.Trojan.EmbeddedPDF-1.
What can we do about this, except disabling PUA?
p.
___
Help us build a comprehensive ClamAV guide: