blocklist

[haze242]

А зачем убрали возможность отключать отдельные правила блоклиста?
Теперь если что-то сломалось только отключать весь список...

Мне например нужно отключить 13.107.21.200 в extra, чтобы иметь возможность использовать сервисы Bing ( перевод в qtranslate и textractor, поиск по картинкам в браузерах ), а теперь я это могу сделать только отключив весь список extra ( пытался вручную создать правило, но видимо блоклист имеет более высокий приоритет ).

[ltguillaume]

I agree, this is awful. I'm going back to v2 because of this...

What's even worse: I had all rules enabled, but after updating to v3.x only the telemetry rules were enabled. Without any notification, my settings were abruptly changed!

[henrypp]

Without any notification, my settings were abruptly changed!

Previous rules are backed up. And v.3.0.1 did not made changes for old profile.

[henrypp]

Ничего менять не буду.

#384
#395
#370
#206
#229
#240
#244
#359
#11

...и ещё over9k на всех форумах где люди с кривыми правилами не могут включить обоссаные обновления

[haze242]

Ничего менять не буду.

Как вариант, можно было бы запилить какой-нибудь "режим эксперта"... ( ну это если интересно )

А нет какого-нибудь способа вручную сделать исключение для одного айпишника? ( не обязательно из интерфейса, возможно там через какой-нибудь конфиг )

[ltguillaume]

@henrypp I have checked the issues you listed and most don't have anything to do with the blocklist (most are duplicates and actually because of issues with svchost.exe being blocked), and most certainly will not be resolved by the new behavior in v3, so I don't really know what you mean here.

You will always keep people who need help understanding how things work. The problem is that by removing the individual blocklist entries from the program, you'll make the process even less transparent, and a lot less useful. I really think it would be much better to reverse this decision.

Previous rules are backed up. And v.3.0.1 did not made changes for old profile.

Sorry, but that is simply not true. The two options for update and extra were disabled by simplewall, not by me. All the individual blocklist rules were checked in v2 before updating to v3. I made a backup, so I could double-check.

@haze242 I've opted for separate handling of blocked connections because of the blocklist here The blocklist (in its old form) would be fantastic with more granular settings, as proposed in that issue.

[ltguillaume]

Another solution would be to be able to allow certain IP's from the blocklists for specific apps via custom rules. This way, you could keep the new behavior, but it wouldn't be an all-or-nothing solution anymore (which isn't a solution all imho). This also hooks into this idea.

[Matthaiks]

IMHO, simplewall should have an option to load self-provided WindowsSpyBlocker's blocklist.xml files.

[ltguillaume]

@Matthaiks I disagree. The WindowsSpyBlocker lists change regularly, so providing your own list would create a false sense of blocking all traffic. If the implementation would allow for a blocklist rule to be temporarily disabled (so, with a timer), I think simplewall's implementation would be great. See #380.