Joseph L. Casale a écrit : > Exact scenario occurred for me as well. > Hi everyone, here again, on a brand new install with 2.1.2, an old oink and a brand new one... it all end up with the same result, md5 error first and invalid oink after this...
But it does not end here... I tried the content filter in order to prove my customer that it can be useful... Bad Idea !!! I tried to put on all the porno and sexual things and typed www.grosseins.com (bigboobs.com should exist also in english...)... I was quite amazed that i can access the site without any trouble... I did also put http://www.grosseins.com in the black list, but it also failed to block the site.... Is the oink code related to the content filter or a snort general problem on this version ? I don't know... What I know is that the "mother who wanted her kid to be protected by the content filter" had quite surprise to see i did not work as it should... Stephane ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Efw-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/efw-user
