Date: Wed, 29 May 2019 16:36:33 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 238220] security/snort Message-ID: <bug-238220-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D238220 Bug ID: 238220 Summary: security/snort Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: Individual Port(s) Assignee: zi@FreeBSD.org Reporter: bmeeks8@bellsouth.net Assignee: zi@FreeBSD.org Flags: maintainer-feedback?(zi@FreeBSD.org) There can be an issue created by ambiguous use of 'yacc' instead of 'bison' when compiling the target-based modules in the Snort binary. If 'yacc' is used, then the resulting binary will fail to read Host Attributes table XML files. The code will report a fatal syntax error and exit even when the XML file is actually properly formatted. When 'bison' is used instead in the s= ame builder environment, the resulting Snort binary will properly read the XML = file for the Host Attributes table. I was able to prevent this issue from happening by adding 'bison' to the US= ES=3D line in the Snort Makefile. This forces the compiler to use 'bison' during= the build. Suggest adding 'bison' to the USES=3D line in the Makefile as it appears the compilation process produces a faulty Snort binary when 'yacc' is used on FreeBSD. It seems 'yacc' can be the default in some FreeBSD build environm= ents and will be used when no preference is specified in the Makefile. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-238220-7788>