This is an automated email from the ASF dual-hosted git repository.
fanningpj pushed a commit to branch 1.0.x
in repository https://gitbox.apache.org/repos/asf/incubator-pekko.git
The following commit(s) were added to refs/heads/1.0.x by this push:
new a40d160601 remove mpl licensed file (#810) (#812)
a40d160601 is described below
commit a40d16060139303b9b00b6a1a957cbc621e9251d
Author: PJ Fanning <[email protected]>
AuthorDate: Wed Nov 22 13:28:40 2023 +0100
remove mpl licensed file (#810) (#812)
---
actor-tests/src/test/bind/etc/bind.keys | 50 ---------------------------------
1 file changed, 50 deletions(-)
diff --git a/actor-tests/src/test/bind/etc/bind.keys
b/actor-tests/src/test/bind/etc/bind.keys
deleted file mode 100755
index 5e5a32ba9c..0000000000
--- a/actor-tests/src/test/bind/etc/bind.keys
+++ /dev/null
@@ -1,50 +0,0 @@
-# The bind.keys file is used to override the built-in DNSSEC trust anchors
-# which are included as part of BIND 9. The only trust anchors it contains
-# are for the DNS root zone ("."). Trust anchors for any other zones MUST
-# be configured elsewhere; if they are configured here, they will not be
-# recognized or used by named.
-#
-# The built-in trust anchors are provided for convenience of configuration.
-# They are not activated within named.conf unless specifically switched on.
-# To use the built-in key, use "dnssec-validation auto;" in the
-# named.conf options. Without this option being set, the keys in this
-# file are ignored.
-#
-# This file is NOT expected to be user-configured.
-#
-# These keys are current as of October 2017. If any key fails to
-# initialize correctly, it may have expired. In that event you should
-# replace this file with a current version. The latest version of
-# bind.keys can always be obtained from ISC at https://www.isc.org/bind-keys.
-#
-# See https://data.iana.org/root-anchors/root-anchors.xml
-# for current trust anchor information for the root zone.
-
-managed-keys {
- # This key (19036) is to be phased out starting in 2017. It will
- # remain in the root zone for some time after its successor key
- # has been added. It will remain this file until it is removed from
- # the root zone.
- . initial-key 257 3 8
"AwEAAagAIKlVZrpC6Ia7gEzahOR+9W29euxhJhVVLOyQbSEW0O8gcCjF
- FVQUTf6v58fLjwBd0YI0EzrAcQqBGCzh/RStIoO8g0NfnfL2MTJRkxoX
- bfDaUeVPQuYEhg37NZWAJQ9VnMVDxP/VHL496M/QZxkjf5/Efucp2gaD
- X6RS6CXpoY68LsvPVjR0ZSwzz1apAzvN9dlzEheX7ICJBBtuA6G3LQpz
- W5hOA2hzCTMjJPJ8LbqF6dsV6DoBQzgul0sGIcGOYl7OyQdXfZ57relS
- Qageu+ipAdTTJ25AsRTAoub8ONGcLmqrAmRLKBP1dfwhYB4N7knNnulq
- QxA+Uk1ihz0=";
-
- # This key (20326) was published in the root zone in 2017.
- # Servers which were already using the old key (19036) should
- # roll seamlessly to this new one via RFC 5011 rollover. Servers
- # being set up for the first time can use the contents of this
- # file as initializing keys; thereafter, the keys in the
- # managed key database will be trusted and maintained
- # automatically.
- . initial-key 257 3 8
"AwEAAaz/tAm8yTn4Mfeh5eyI96WSVexTBAvkMgJzkKTOiW1vkIbzxeF3
- +/4RgWOq7HrxRixHlFlExOLAJr5emLvN7SWXgnLh4+B5xQlNVz8Og8kv
- ArMtNROxVQuCaSnIDdD5LKyWbRd2n9WGe2R8PzgCmr3EgVLrjyBxWezF
- 0jLHwVN8efS3rCj/EWgvIWgb9tarpVUDK/b58Da+sqqls3eNbuv7pr+e
- oZG+SrDK6nWeL3c6H5Apxz7LjVc1uTIdsIXxuOLYA4/ilBmSVIzuDWfd
- RUfhHdY6+cn8HFRm+2hM8AnXGXws9555KrUB5qihylGa8subX2Nn6UwN
- R1AkUTV74bU=";
-};
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
