search

warvair / peerblock

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

Warn if close while blocking traffic recently #95

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
If PeerBlock has blocked some packets recently (TBD: within the past five
minutes or so?), we should warn the user about closing PeerBlock.  They may
not have realized that they're still running e.g. a P2P app in the
background, and it would be nice if we could help them avoid running
unprotected.

An additional thought might be to check the list of running processes
against a list of known filesharing apps, so we can warn them if for
example they're still running a "dangerous" app when they try to exit
PeerBlock.

Original issue reported on code.google.com by peerbloc...@gmail.com on 12 Sep 2009 at 6:04

GoogleCodeExporter commented 9 years ago 
Removing 'After1.0' release-targetting.

Original comment by peerbloc...@gmail.com on 29 Sep 2009 at 3:58

GoogleCodeExporter commented 9 years ago

Original comment by peerbloc...@gmail.com on 30 Sep 2009 at 4:34

GoogleCodeExporter commented 9 years ago 
i think anyone using any sort of p2p would say 5min is a bit high and 1min 
might work

Original comment by neonligh...@gmail.com on 15 Nov 2009 at 9:25

GoogleCodeExporter commented 9 years ago 
This issue was closed by revision r298.

Original comment by peerbloc...@gmail.com on 24 Feb 2010 at 8:37

GoogleCodeExporter commented 9 years ago 
Implemented in the SVN r298 commit, will be present in the next Beta Release.

We're defaulting to a 60-second wait period, meaning that if a non-HTTP block 
was
seen in the 60 seconds prior to you attempting to exit PeerBlock it will warn 
you
that traffic's occurred recently and ask you to confirm that you really want to 
exit.  

This 60-seconds value can be user-configured, but not via the PeerBlock UI - 
there
simply isn't enough space for another option at this point, and I would expect 
that
only a very small portion of our users would care about this.  If you want to 
change
this value, you can edit peerblock.conf (while PeerBlock is not running) and 
change
the "RecentBlockWarntime" value from 60 to some other value.  The value is the 
number
of seconds for which we'd like to see no Blocks; a value of 0 will disable it.

The "warning message" it will pop up can be seen here, if you're interested:
http://img199.imageshack.us/img199/5072/ss20100224154553.png

Original comment by peerbloc...@gmail.com on 24 Feb 2010 at 8:46