File hash security filter not working?

[cgreevey]

According to http://sourceforge.net/apps/mediawiki/s ... _Filtering a Content filter of

urn:sha1:FILEHASHFILEHASHFILEHASHFILEHASH

should block a specific file (no matter how it is renamed) from search results.

This doesn't seem to work in 2.5.5.0. To test, I right clicked a search result, "Copy URI", and picked the bottom one, the one of the form:

http://nnn.nnn.nnn.nnn:port/uri-res/N2R?urn:sha1:FILEHASHFILEHASHFILEHASHFILEHASH

then pasted into a new security rule, deleting everything left of "urn:sha1:" and leaving that and everything right of it. I didn't bother with the comment field, set it as a content rather than an IP filter, and set it not to expire automatically. Shareaza spent a while "thinking" and then ... nothing. The rule shows 0 hits and the search result I chose to test it on didn't disappear. Using a word in that result's filename as a content filter, by contrast, does work.

Setting "match any", "match all", or "reg. exp." makes no difference: I tried all three and none work with a hash as the filter content.

Since I used copy and paste and didn't edit anything from "urn:sha1:" onward, there's no possibility that the hash was mistyped and thus doesn't actually correspond to the targeted search result.

So, it looks like either the wiki's description of how to block by hash is wrong/out of date or 2.5.5.0 has a bug that prevents this feature from working as intended.

Does anyone here know which, or know of an effective workaround?

[skinvista]

Long-standing unaddressed issue where any non-regex or IP rule is never properly tested.
Should be simply fixed in r9081.
Please try the next Debug build. (2012-02-10 / r9081 or better)

[ailurophobe]

Thanks, Hash blocks make search much nicer...