Feature #9874
closedsafesearch enforcing
100%
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
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/
Files
Updated by Viktor Gurov almost 5 years ago
- DuckDuckGo: duckduckgo.com CNAME safe.duckduckgo.com (54.229.105.151)
see https://help.duckduckgo.com/duckduckgo-help-pages/features/safe-search/
Updated by Viktor Gurov almost 5 years ago
Updated by Viktor Gurov almost 5 years ago
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)
Updated by Viktor Gurov over 4 years 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
Updated by Jim Pingle over 4 years ago
- Status changed from New to Pull Request Review
Updated by Renato Botelho over 4 years 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!
Updated by Grimson Gretzleburg over 4 years 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/".
Updated by Viktor Gurov over 4 years 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!
Updated by Jim Pingle over 4 years ago
- Status changed from Feedback to Pull Request Review
Updated by Renato Botelho over 4 years ago
- Status changed from Pull Request Review to Feedback
PR has been merged. Thanks!
Updated by Viktor Gurov over 4 years ago
- Status changed from Feedback to Resolved
pfBlockerNG 2.2.5_32
works as expected
Updated by Viktor Gurov about 4 years ago
Minor WebGUI fix:
https://github.com/pfsense/FreeBSD-ports/pull/863
Updated by Jim Pingle about 4 years ago
- Status changed from Resolved to Pull Request Review
Updated by Renato Botelho about 4 years ago
- Status changed from Pull Request Review to Feedback
PR has been merged. Thanks!