Open GoogleCodeExporter opened 8 years ago
Sorry that was v1.1 release 518.
Original comment by james.ha...@gmail.com
on 23 Nov 2010 at 10:24
Yes, many people were complaining that they'd disable PeerBlock then exit it
(or reboot), and when they would next start PeerBlock (or their machine)
PeerBlock would be disabled . . . and they'd be unprotected, without realizing
it. We determined that "most" users expected PeerBlock to always start up as
Enabled, but that if they had previously permanently Allowed HTTP they'd expect
_that_ setting to "stick". So that's what it now does.
I'd thought we'd put in an "Advanced Option" (meaning you need to hand-edit
your config file) to override this behavior, but I can't find it. We'll leave
this bug open until we do put that in. Changing the bug-description to more
accurately describe the intended change here, and targetting for the first
1.1.x bugfix-release.
Original comment by peerbloc...@gmail.com
on 24 Nov 2010 at 5:01
Original issue reported on code.google.com by
james.ha...@gmail.com
on 23 Nov 2010 at 10:21