Snort and Suricata (not at same time) Emerging Threats and VRT Rules MD5 mismatc

[renolatino]

Hi all,

First off, thanks in advanced for the help.

When I try to update rules, the Emerging Threat and VRT Rules show status of not downloaded.  When reviewing the logs, I get a mismatch for the MD5 sums.  The next line in the log shows Emerging Threat and VRT rules not updated.

This also happened when I had Suricata installed instead of Snort (and was why I switched back to Snort).

Any help as to why the MD5's aren't the same would be helpful.  And as of this post, I am on the latest version of pfSense.

The logs read: Downloading file 'emerging.rules.tar.gz'…
Done downloading rules file.
Emerging Threats Open rules file download failed.  Bad MD5 checksum.
Downloaded Emerging Threats Open rules file MD5: bd06014a207828fddc4a21fda4e4646d
Expected Emerging Threats Open rules file MD5: 3ff6bf86216bafa912112283998d466b
Emerging Threats Open rules file download failed.  Emerging Threats Open rules will not be updated.

This happens even when I check the disable checksum checking with snort to improve performance on the <Snort Interfaces/Wan Settings tab.  And also when I click Force Update in the updates tab.

Thanks again for your help.

R

[doktornotor]

@renolatino:

Any help as to why the MD5's aren't the same would be helpful.  And as of this post, I am on the latest version of pfSense.

You need to ask upstream why they are so lame that they manage to screw the checksums about 10 times every month.

[seanmcb]

And why on earth is security software still using MD5?! :(