/netbsd-src/external/mpl/bind/dist/doc/dnssec-guide/ |
H A D | troubleshooting.rst | 156 validating www.example.org/A: no valid signature found 176 validating. DNSSEC-related messages are not recorded in :any:`syslog` by default, 209 successfully looking up and validating the domain name ``ftp.isc.org``. 213 validating ./NS: starting 214 validating ./NS: attempting positive response validation 215 validating ./DNSKEY: starting 216 validating ./DNSKEY: attempting positive response validation 217 validating ./DNSKEY: verify rdataset (keyid=20326): success 218 validating ./DNSKEY: marking as secure (DS) 219 validating [all...] |
H A D | introduction.rst | 116 validating resolver, how to sign DNS zone data, and other operational 160 servers, also known as validating resolvers, to verify the answers 205 With DNSSEC validation enabled, a validating recursive name server 206 (a.k.a. a *validating resolver*) asks for additional resource 210 validating resolver performs cryptographic computation to verify the 215 the validating resolver reaches a key that it trusts. In the ideal, 216 fully deployed world of DNSSEC, all validating resolvers only need to 224 The following example shows the 12 steps of the DNSSEC validating process 231 the validating resolver follows standard DNS protocol to track down 242 3. The validating resolve [all...] |
H A D | validation.rst | 23 working DNSSEC-aware recursive server, also known as a validating 24 resolver. A validating resolver performs validation for each remote 54 now happily validating each DNS response. If this does not work for you, 106 is indeed validating DNS queries is to use one of the many web-based 111 confirm that it is in fact validating DNS responses. 125 validating resolver yourself. 425 that process now and see what your validating resolver is doing in more 429 1. The validating resolver queries the ``isc.org`` name servers for the 438 3. The validating resolver queries for the DNSKEY for ``isc.org``. 443 5. The validating resolve [all...] |
H A D | commonly-asked-questions.rst | 65 validating resolver can still look up all of these domain names as it always 84 A DNSSEC-enabled validating resolver still resolves :term:`Secure` and 93 behavior among DNS servers, not between a DNS server (validating resolver) and 112 the full benefit of DNSSEC, as other validating resolvers are not 114 zone, other validating resolvers treat your zone as an insecure 124 while DNSSEC secures DNS lookup by validating answers. Even if you enable
|
H A D | preface.rst | 32 :ref:`dnssec_validation` walks through setting up a validating 34 some examples of tools to verify that the resolver is properly validating
|
H A D | getting-started.rst | 38 Enabling DNSSEC validation on a recursive server makes it a *validating 39 resolver*. The job of a validating resolver is to fetch additional 43 1. *CPU*: a validating resolver executes cryptographic functions on cache-miss
|
/netbsd-src/external/gpl3/binutils.old/dist/gprofng/src/ |
H A D | SAXParserFactory.h | 51 validating = _validating; in setValidating() 63 return validating; in isValidating() 71 bool validating; variable
|
/netbsd-src/external/gpl3/binutils/dist/gprofng/src/ |
H A D | SAXParserFactory.h | 51 validating = _validating; in setValidating() 63 return validating; in isValidating() 71 bool validating; variable
|
/netbsd-src/external/bsd/unbound/dist/contrib/ |
H A D | libunbound.pc.in | 7 Description: Library with validating, recursive, and caching DNS resolver
|
H A D | unbound.spec | 14 Unbound is a validating, recursive, and caching DNS resolver.
|
/netbsd-src/usr.sbin/npf/npfctl/ |
H A D | npf_show.c | 69 bool validating; member 678 dval = ctx->validating ? NULL : &defval; in npfctl_print_params() 701 ctx->validating = false; in npfctl_config_show() 710 ctx->validating = true; in npfctl_config_show()
|
/netbsd-src/crypto/external/bsd/openssl/dist/doc/internal/man3/ |
H A D | ossl_cmp_msg_check_update.pod | 59 Note that it does not help validating the message before storing the extraCerts 70 This way these certs are available for validating subsequent messages in the
|
/netbsd-src/external/bsd/unbound/dist/doc/ |
H A D | FEATURES | 28 RFC 4033-4035: as a validating caching server (unbound daemon). 29 as a validating stub (libunbound).
|
/netbsd-src/external/mpl/bind/dist/doc/arm/ |
H A D | managed-keys.inc.rst | 25 To configure a validating resolver to use :rfc:`5011` to maintain a trust 38 Any validating resolver which is configured to use the active KSK as an
|
/netbsd-src/external/mpl/bind/dist/doc/notes/ |
H A D | notes-9.18.8.rst |
|
H A D | notes-9.18.6.rst |
|
/netbsd-src/external/bsd/unbound/dist/ |
H A D | README.md | 9 Unbound is a validating, recursive, caching DNS resolver. It is designed to be
|
/netbsd-src/external/gpl2/texinfo/dist/makeinfo/ |
H A D | makeinfo.h | 227 DECLARE (int, validating, 1);
|
H A D | makeinfo.c | 507 { "no-pointer-validate", 0, &validating, 0 }, 509 { "no-validate", 0, &validating, 0 }, 799 validating = 0; in main() 801 if (!validating) in main() 1754 if (validating) in convert_from_loaded_file()
|
/netbsd-src/external/gpl3/gdb/dist/zlib/contrib/minizip/ |
H A D | MiniZip64_info.txt | 43 Used when debugging and validating the creation of zip files using MiniZip64
|
/netbsd-src/common/dist/zlib/contrib/minizip/ |
H A D | MiniZip64_info.txt | 43 Used when debugging and validating the creation of zip files using MiniZip64
|
/netbsd-src/external/gpl3/gdb.old/dist/zlib/contrib/minizip/ |
H A D | MiniZip64_info.txt | 43 Used when debugging and validating the creation of zip files using MiniZip64
|
/netbsd-src/external/gpl3/binutils/dist/zlib/contrib/minizip/ |
H A D | MiniZip64_info.txt | 43 Used when debugging and validating the creation of zip files using MiniZip64
|
/netbsd-src/external/gpl3/binutils.old/dist/zlib/contrib/minizip/ |
H A D | MiniZip64_info.txt | 43 Used when debugging and validating the creation of zip files using MiniZip64
|
/netbsd-src/crypto/external/bsd/openssl/dist/doc/man1/ |
H A D | openssl-cmp.pod.in | 375 Trusted certificate(s) to use for validating the newly enrolled certificate. 540 when validating signature-based protection of CMP response messages. 565 when validating server certificates (checking signature-based 566 CMP message protection) and when validating newly enrolled certificates. 598 Ignore key usage restrictions in CMP signer certificates when validating 665 and for validating incoming messages that have MAC-based protection. 863 Trusted certificate(s) to use for validating the TLS server certificate. 1015 Intermediate CA certs that may be useful when validating client certificates.
|