Won't block HTTP connections unless you update first.
Opened this issue · 1 comments
GoogleCodeExporter commented
What steps will reproduce the problem?
1.Unplug the ethernet cable
2.Let peerblock fail updating
3.Monitor the protection screen.
What is the expected output? What do you see instead?
It should not require an update on every start up for it to start blocking
HTTP (blue on the screen) connections.
What version of PeerBlock are you using? On what operating system? 32- or
64-bit?
1.0+ r484 - Windows 7 ultimate x64
Please provide any additional information below. Make sure to attach
peerblock.log and/or any screenshots that would help explain your problem.
Original issue reported on code.google.com by panele...@gmail.com on 6 May 2013 at 3:08
Attachments:
GoogleCodeExporter commented
It was by design to auto-set everything or at least the failed list to "Allow"
(and also, "Allow" seems to be of higher priority than "Block") when there are
something failed updating (with the logs marked as "Auto allow for updating")
because the list cache is temporary... Honestly, I really don't think this is a
feasible option as it compromises security...
I think PeerBlock should change to, that when specifying an online list,
requires specifying a persistent local file path as the cache (the file can be
a valid existing file), and when update failed while the cache file is present,
load the specified local cache file like any other local block list file
instead, and make the block function as it used to. The persistent cache file
must not be touched during the update process, until the update has been
successfully carried out.
Honestly I haven't used it ever since I updated to Windows 8 and found out it
couldn't autostart anymore... If it is working again, I'll definitely use it
again.
Original comment by Slytheri...@gmail.com on 31 May 2013 at 6:49