[Emerging-Sigs] 2522000 rev:3904

Jason Williams jwilliams at emergingthreats.net
Tue Dec 10 07:23:13 HST 2019


Yea, we changed some code on the backend for generating these rules and
added some new sources. As it turns out it all worked fine by hand, but
somehow automation stuck a new line in there. This is fixed now. Thanks!

On Tue, Dec 10, 2019 at 10:05 AM Jack Mott <jmott at emergingthreats.net>
wrote:

> Hi Tiago,
>
> Nice catch! We will get this updated for today's release.
>
> Best,
>
> Jack
>
> On Tue, Dec 10, 2019 at 9:38 AM Tiago Faria <tiago.faria.backups at gmail.com>
> wrote:
>
>> Hi,
>>
>> Believe there is a problem with this rule:
>>
>> "alert tcp [*,*
>> 103.15.28.215,103.208.220.122,103.208.220.226,103.234.220.195..."
>>
>> ^ comma
>>
>> TY!
>> T
>> _______________________________________________
>> 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
>>
>> _______________________________________________
> 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/20191210/a52edf6b/attachment-0001.html>


More information about the Emerging-sigs mailing list