I'd guess it would too; great suggestion. Since spammers can change ip addresses frequently. Eventually some innocent good gnutella sharers may be blocked via your ban list if ip's are banned.

How do we ban the specific SHA1 file code?

Well unfortunately banning SHA1 is not as comfortable as banning hosts. But you can build yourself a search file rule like this:

When receiving search results
with 'urn:sha1:ABC...' or 'urn:sha1:XYZ...' as file urns

Choose one of:
ban their source (for 7 days)
delete them
hide them

And enable the rule permanently.

When you find a new SHA1 you need to add it manually.


I know this is not the ideal solution... but its the only think I can offer right now.
To help a little the search table supports row based Copy&Paste by shortcut keys. On Windows CTRL-C. Just copy the line, paste it into some editor and extract the SHA1.

Hope that helps at least a little....

__________________