From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. f617fd912ba2ae3b3c1aad74506977c43bd128df
Date: Wed, 22 May 2019 15:30:02 +0100 [thread overview]
Message-ID: <20190522143003.208C284FDC8@people01.i.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1617 bytes --]
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".
The branch, next has been updated
via f617fd912ba2ae3b3c1aad74506977c43bd128df (commit)
from 6d653734fb8b044db24f2650c740820a6e0132a0 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit f617fd912ba2ae3b3c1aad74506977c43bd128df
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Wed May 22 15:29:32 2019 +0100
unbound: Safe Search: Enable Restrict-Moderate for YouTube
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
src/initscripts/system/unbound | 4 ++++
1 file changed, 4 insertions(+)
Difference in files:
diff --git a/src/initscripts/system/unbound b/src/initscripts/system/unbound
index 3e372ff65..520525ea1 100644
--- a/src/initscripts/system/unbound
+++ b/src/initscripts/system/unbound
@@ -707,6 +707,10 @@ write_safe_search_conf() {
# Yandex
echo " local-zone: yandex.ru transparent"
echo " local-data: \"yandex.ru A 213.180.193.56\""
+
+ # YouTube
+ echo " local-zone: youtube.com transparent"
+ echo " local-data: \"www.youtube.com CNAME restrictmoderate.youtube.com.\""
) > /etc/unbound/safe-search.conf
}
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2019-05-22 14:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190522143003.208C284FDC8@people01.i.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox