Re: Pulledpork 0.74 and Ubuntu 18.04 so_rules

[Michael Shirk via Snort-users <snort-users () lists snort org>]

Anything that is not working correctly, such as a missing error
message, please raise as an issue on github to fix it. The interesting
thing is Ubuntu-18-4 and FC-30 both have the underscore in the
directory name from the rules file. This one may be better fixed by
Talos, but the code can be updated to handle either/or.

https://github.com/shirkdog/pulledpork

As to the so_rules together with text rules, this has been the design
for a while, with the path of your so_rules as a configuration item in
pulledpork.conf but the rules being placed in the single rule file.

I will be "hopefully" working up a 0.7.4 release for some fixes that
have been out there for a while soon, and snort-3.0 rule processing is
a must for 0.7.4 to be released.

On Tue, Jul 23, 2019 at 8:22 PM Jefferson, Shawn
<Shawn.Jefferson () bcferries com> wrote:
> Hi,
>
> I wanted to bring this to JJC and/or Joel's attention.  I just spent some time troubleshooting why my SO_rules 
> weren't updating with 2.9.14.0 and Pulledpork 0.7.4.  Basically, pulledpork.pl is manipulating the arch retrieved 
> from uname -a to change the "_" to a "-".  All the Ubuntu precompiled so_rules have a directory structure listed as 
> "x86-64" EXCEPT for Ubuntu-18-4, which has "x86_64".  Commenting out the replacement in pulledpork.pl fixed it for 
> me, but I guess there should be an official fix either from JJC or Snort/Talos.  Also, Pulledpork just fails silently 
> to update your SO rules if it can't find the $Distro/$arch files.  Maybe an error or warning message? ;)
>
> PS. A complaint (?), or maybe more of a discussion point about the recent version of pulledpork.  Now (admittedly 
> it's been a while since I've updated) that pulledpork insists on putting the so_rules into the main file instead of 
> giving you a choice, it's difficult (impossible?) to update your text rules separately from your so_rules.  I was 
> updating my text rules twice a day, and only updating my so_rules once a week since a so_rule update requires a 
> restart of the snort process instead of just a reload.  Maybe I should be updating text and so_rules at the same time 
> though?  I guess I could be missing rule updates that are important to get quickly by only updating so_rules once a 
> week.  For now I have decided to update text and so_rules at the same time and live with the restart of the snort 
> processes.  However, I think more choice in what pulledpork does with your so_rules is better, but perhaps there's a 
> reason the sostub_path option was deprecated?
>
> Thanks,
> Shawn
> _______________________________________________
> Snort-users mailing list
> Snort-users () lists snort org
> Go to this URL to change user options or unsubscribe:
> https://lists.snort.org/mailman/listinfo/snort-users
>
>         To unsubscribe, send an email to:
>         snort-users-leave () lists snort org
>
> Please visit http://blog.snort.org to stay current on all the latest Snort news!
>
> Please follow these rules: https://snort.org/faq/what-is-the-mailing-list-etiquette



-- 
Michael Shirk
Daemon Security, Inc.
https://www.daemon-security.com
_______________________________________________
Snort-users mailing list
Snort-users () lists snort org
Go to this URL to change user options or unsubscribe:
https://lists.snort.org/mailman/listinfo/snort-users

        To unsubscribe, send an email to:
        snort-users-leave () lists snort org

Please visit http://blog.snort.org to stay current on all the latest Snort news!

Please follow these rules: https://snort.org/faq/what-is-the-mailing-list-etiquette