[Emerging-Sigs] Issue Disabling SID 2018959
Jason Williams
jwilliams at emergingthreats.net
Wed Apr 24 13:34:35 HDT 2019
Matt,
This just looks like a typo to me, getting it fixed up for today's release.
Thanks!
On Wed, Apr 24, 2019 at 3:34 PM Matthew Clairmont (R* NYC) <
Matthew.Clairmont at rockstargames.com> wrote:
> Greetings,
>
>
>
> After several hours of playing with this issue, I came across the below
> comment on the signature describing the exact issue I’m having. When
> putting 1:2018959 into disabledsid.conf and running pulledpork again, it
> does not disable the signature, however, I can disable it’s reference SID
> 2000419 (amongst 30+ others) without issue. Has anyone successfully
> disabled both of these recently with pulledork v0.7.3 and Suricata 4.1.3?
>
>
>
> https://doc.emergingthreats[.]net/bin/view/Main/2018959
>
>
>
> Thanks,
>
> Matt
> _______________________________________________
> Emerging-sigs mailing list
> Emerging-sigs at lists.emergingthreats.net
> https://lists.emergingthreats.net/mailman/listinfo/emerging-sigs
>
> Support Emerging Threats! Subscribe to Emerging Threats Pro
> http://www.emergingthreats.net
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.emergingthreats.net/pipermail/emerging-sigs/attachments/20190424/ebf3209c/attachment.html>
More information about the Emerging-sigs
mailing list