burstas / peerblock

Automatically exported from code.google.com/p/peerblock
Other
0 stars 0 forks source link

Change the logic when giving permanent block to IP addresses #272

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
As of r277 release, PeerBlock adds the wanted IP address into
permblock.p2b/permallow.p2b whenever user adds a permanent block/allow via
PeerBlock GUI. Because of PeerBlock's feature on giving allow list
priority, the newly added permanent block will have zero effect if the same
IP address happens to have been permanent allowed in the past.

What I suggest is that whenever user adds a permanent block to IP address
X, PeerBlock will add X to permblock.p2b and remove X from permallow.p2b,
if permallow.p2b happens to have the same IP address X that the user just
blocked.

Original issue reported on code.google.com by tippy%pe...@gtempaccount.com on 26 Feb 2010 at 4:34

GoogleCodeExporter commented 8 years ago
As of r277, PeerBlock generates the cache.p2b (the file used to determine what
PeerBlock blocks) by adding all IP addresses in lists set up as block (including
permblock.p2b) and then subtracts the IP addresses according to the lists set 
up as
allow (including permallow.p2b).

Perhaps the logic could be changed lik this: Gather all list's IP addresses 
that are
set to block -> remove IP addresses according to the lists that are set to 
allow ->
add IP addresses according to permblock.p2b -> remove IP addresses according to
permallow.p2b? This would give user manually added block/allow more priority.

Original comment by tippy%pe...@gtempaccount.com on 26 Feb 2010 at 4:41

GoogleCodeExporter commented 8 years ago

Original comment by peerbloc...@gmail.com on 26 Feb 2010 at 4:46