Feature #9874: safesearch enforcing - pfSense Packages - pfSense bugtracker

Feature #9874

safesearch enforcing

Added by Viktor Gurov 8 months ago. Updated 24 days ago.

Status:

Resolved

Priority:

Normal

Assignee:

Renato Botelho

Category:

pfBlockerNG

Target version:

Start date:

11/02/2019

Due date:

% Done:

100%

Estimated time:

Description

Add ability to force safesearch via special DNS entries.

Google: 216.239.38.120 google.com
see https://support.google.com/websearch/answer/186669?hl=en
Bing: www.bing.com CNAME strict.bing.com
see https://help.bing.microsoft.com/#apex/18/en-us/10003/0
Yandex: 213.180.193.56 yandex.ru
see https://yandex.com/support/search/schoolsearch.html#schoolsearch__hosts
YouTube
add a CNAME for the following records:
www.youtube.com
m.youtube.com
youtubei.googleapis.com
youtube.googleapis.com
www.youtube-nocookie.com

For Strict Restricted YouTube access, add restrict.youtube.com as a CNAME for these domains. For Moderate Restricted YouTube access, add restrictmoderate.youtube.com as a CNAME for these domains.
see https://support.opendns.com/hc/en-us/articles/227986807-How-to-Enforcing-Google-SafeSearch-YouTube-and-Bing

Pixabay: www.pixabay.com CNAME safesearch.pixabay.com
see https://pixabay.com/blog/posts/block-adult-content-on-pixabay-at-your-school-or-w-140/

Screenshot from 2019-11-09 11-59-01.png (61 KB) Screenshot from 2019-11-09 11-59-01.png	GUI screenshot	Viktor Gurov, 11/09/2019 02:59 AM
Screenshot from 2019-11-10 12-22-57.png (61.8 KB) Screenshot from 2019-11-10 12-22-57.png	last WebGUI screenshot	Viktor Gurov, 11/10/2019 03:25 AM

History

#1 Updated by Viktor Gurov 8 months ago

DuckDuckGo: duckduckgo.com CNAME safe.duckduckgo.com (54.229.105.151)
see https://help.duckduckgo.com/duckduckgo-help-pages/features/safe-search/

#2 Updated by Viktor Gurov 8 months ago

File Screenshot from 2019-11-09 11-59-01.png Screenshot from 2019-11-09 11-59-01.png added

https://github.com/pfsense/FreeBSD-ports/pull/701

#3 Updated by Viktor Gurov 8 months ago

File Screenshot from 2019-11-10 12-22-57.png Screenshot from 2019-11-10 12-22-57.png added

PR updated with Firefox DoH blocking support
(see https://forum.netgate.com/topic/133679/heads-up-be-aware-of-trusted-recursive-resolver-trr-in-firefox/38)

#4 Updated by Viktor Gurov 8 months ago

received email from Yandex support with the list of domains for redirection:

The main Yandex.Search domains for which we recommend filtering:

yandex.ru
yandex.ua
yandex.by
yandex.ee
yandex.lt
yandex.lv
yandex.md
yandex.uz
yandex.tm
yandex.tj
yandex.az
ya.ru
yandex.com

#5 Updated by Jim Pingle 8 months ago

Status changed from New to Pull Request Review

#6 Updated by Renato Botelho 2 months ago

Status changed from Pull Request Review to Feedback
Assignee set to Renato Botelho
% Done changed from 0 to 100

PR has been merged. Thanks!

#7 Updated by Grimson Gretzleburg 2 months ago

You forgot to add "/www/pfblockerng/pfblockerng_safesearch.php" to the package meta data, so it's not included in the update and you get an 404 not found error when trying to access the new settings.

Edit, the same applies to the added .conf files in "/usr/local/pkg/pfblockerng/".

#8 Updated by Viktor Gurov 2 months ago

Grimson Gretzleburg wrote:

You forgot to add "/www/pfblockerng/pfblockerng_safesearch.php" to the package meta data, so it's not included in the update and you get an 404 not found error when trying to access the new settings.

Edit, the same applies to the added .conf files in "/usr/local/pkg/pfblockerng/".

Thanks!

Fix:
https://github.com/pfsense/FreeBSD-ports/pull/857