Patch-aa is no longer necessary (creation of correct symlinks to
"razor-client").
This release fixes two recently discovered DoS vulnerabilities: Certain
HTML messages could crash the process and a bug sometimes caused server
discovery to go into an infinite loop.
Changes since version 2.67
==========================
2.72 (June 16, 2005)
+ "razor-client" no longer creates symlinks to itself
upon installation; four new scripts have been added to
the distribution to replace this functionality
("razor-admin", "razor-check", "razor-report",
"razor-revoke").
2.71 (June 15, 2005)
+ A fix to Makefile.PL script to correctly invoke
"razor-client" after installation. Thanks to Liam
Quinn for the patch.
2.70 (June 10, 2005)
+ Fixed preprocessing of unusual HTML messages. This
resolves the segfault issue in razor-agents. [Bug
#1001417]
+ Fixed handling of certain malformed headers.
+ Explicitly specify the record separator as "\n" when
reading files, to ensure that someone else hasn't set
it to undef. [Patch #537813]
+ "razorzone" is no longer supported and has been
removed from the documentation.
+ Allow the config file to set razorhome. [Bug
#1074391]
+ Razor Agents no longer go into an infinite loop when
discovery fails. [Bug #1016039]
+ Properly creates "razor-*" symlinks after installa-
tion. [Bug #874468]
+ Default to PERLPREFIX instead of PREFIX when
installing man5 pages. [Bug #1001320]
+ Removed a call to $sha1->reset() which was breaking
SHA1 calculation. [Bug #1004858]
+ "use_engines" is no longer supported and has been
removed from the documentation. [Bug #1120311]
+ Shuffle the discovery, catalogue, and nomination
server lists after loading them from disk; this pre-
vents razor-agents from always starting with the same
catalogue server.
+ Replace the complex DNS lookup logic for discovery
servers with a single DNS round robin. [Bug #604679]
+ Remove the ICMP ping logic for finding the "fastest"
catalogue server; the configuration option for this
logic is now ignored. [Support #739464]
+ Removed stale engine code for various signature types
that are no longer used.
Changes:
- almost a complete (compatible) rewrite of Razor v1.
- uses new (fuzzy) signature algorithms to better spot 'mutating'
messages
- Spam reports are now validated based on 'reputation' of the submitter
in order to make it easier to eliminate false positives.
- Registration for submitters required.
- Revocation of spam reports is now possible.
Vipul's Razor is a distributed, collaborative, spam detection and
filtering network. Razor establishes a distributed and constantly
updating catalogue of spam in propagation. This catalogue is used
by clients to filter out known spam.