Snort VRT change in Shared Object Rules path name results in failure to extract and update Snort Shared Object Rules when enabled
Plus Target Version:
Affected Plus Version:
Apparently the Snort Vulnerability Research Team recently altered part of the path name inside the Snort Rules Update archive. This results in failure of the Snort package code to properly extract and copy the Shared Object (SO) rules when performing the periodic rules update. A portion of the long directory path in the archive was changed from "x86_64" to "x86-64" (replaced the underscore with a dash).
Updated by Bill Meeks about 1 year ago
Pull Requests https://github.com/pfsense/FreeBSD-ports/pull/1161 and https://github.com/pfsense/FreeBSD-ports/pull/1162 have been submitted against the Development and RELENG_2_6_0 branches, respectively, to fix this issue. Once these requests are approved and merged, this issue can be marked "resolved".
Updated by Jim Pingle about 1 year ago
- Status changed from New to Feedback
PR merged, thanks!