[Feature-Request] - Security and filters in options
 

Extended Security options.
People should be able to choose what the ban option would do.
eg.
Add ban country
Custom ban period
Remove/ban Ultrapeer

Filters
Pernament filters with advanced options.
-Add filters for terms, SHA1, Filesize, Vendor, Type, Score, Rating, Information, Speed
-Add advanced options to the filters, e.g. numbers to have an interval and include "AND", "OR", "NOT" and other logical search operators
-Add preset filters for adult content
-Add preset filters for known bad files (like these, note that "Skrabemand" isn't an actual word but two random danish words pulled toghether)

EDIT:
http://www.phex.org/wiki/index.php/Filter_System
Here's a guide to set the filters options for size, filename, filetype, SHA1.

What's already possible:

Extended Security options.
-------------------------

People should be able to choose what the ban option would do.
eg.
- Custom ban period
- Remove/ban Ultrapeer (a banned host can no longer connect to you)

Filters
------

Pernament filters with advanced options.
-Add filters for terms, SHA1, Filesize, Vendor, Type, Score, Rating, Information, Speed
-Add advanced options to the filters, e.g. numbers to have an interval and include "AND", "OR", "NOT" and other logical search operators
-Add preset filters for adult content
-Add preset filters for known bad files (like these, note that "Skrabemand" isn't an actual word but two random danish words pulled toghether) - this one needs more user input.


So the only missing part is "ban by country", and you can do that manually by banning the correct IP ranges from the security tab.


Would you help us with finding known bad files (so we can add them to the scam file filter)?

Well, you can't add pernament filters for speed, score or rating in the filter rules, but that's really not that important.

I've made these filters
When receiving search results
with a file size at least 72.8 KB and at most 72.8 KB or at least 5,610.0 KB and at most 5,611.0 KB or at least 93.0 KB and at most 100.0 KB or at least 937.0 KB and at most 940.0 KB or at least 2,974.0 KB and at most 2,975.0 KB or at least 3,125.0 KB and at most 3,126.0 KB or at least 3,432.0 KB and at most 3,433.0 KB or at least 3,462.0 KB and at most 3,463.0 KB or at least 3,786.0 KB and at most 3,787.0 KB or at least 3,980.0 KB and at most 3,981.0 KB or at least 75.0 KB and at most 76 bytes or at least 75.4 KB and at most 75.7 KB
hide them
and ban their source (for 7 days)

When receiving search results
with 'urn:sha1:6M4D2F2OLAMRF5SYDAJXKMGBNJL5CPEX' or 'urn:sha1:JYMLNADQONAK3MUH7EQM57ADRE6CPRZA' as file urns
ban their source (for 7 days)

You can see some of the bad files in the pic I posted. Now I don't get those files that pops up in different names. There's some zips at about 75.5 kb that pops up with different SHA1 that you should try figure out, how to get wrid of. This filter I've made isn't optimal cause it bans users just because of the filesize.

Then support from spyware/adware/virus/trojan scanners would ofc. be nice, but that'll slow down the whole network.

Can't you just install one locally?

What would be the advantage of integrating that into Gnutella?

Then it would scan the files before they were finished, and always scan them, which most scanners doen't do, cause they're set to scan when you open a file or only when users does it. Plus, it could run faster if it was integrated.

The problem with banning is that spammers don't have to be honest about their IP.

If many people implemented this kind of automatic banning, spammers could just put the IP of innocent sharers as source into the spam files, and all those good sharers would get banned.

Deleting the files might do the trick, too.

Could you test that?

Since the files are transferred in chunks, scanning while you transmit might not be easily possible.

What I can imagine as useful would be to let Phex trigger an installed scanner (when one is available) automatically when the download finished.

But I don't know, if that currently is technically possible.

i would think that a better possibility is to set an Antivirus program to scan the download folder whenever new files show up. That wouldn't strain Phex and the Antivirus is just doing the job, it was supposed to do in the first place.

Well, that's just a normal scanner. The problem with that is that the scanner has to scan every file that runs through the computer, which means that you will use twice the resource of a machine for same work.


If you let the scanner only be activated, then the file is down, then you won't have a scanner always scanning the folder. (Difference is, to let phex trigger the scanner, and not have a seperate scanner to moniter the whole time)

And It would be possible to scan the chunks too, because they can have early signs of known infections. But this will be difficult to do, because phex is already using the chunks.