HomeSort by relevance Sort by last modified time
    Searched refs:dnssec (Results 1 - 5 of 5) sorted by null

  /external/chromium/net/base/
dnsrr_resolver.h 42 // dnssec is true if the response was DNSSEC validated.
43 bool dnssec; member in struct:net::RRResponse
79 // Try harder to get a DNSSEC signed response. This doesn't mean that the
80 // RRResponse will always have the dnssec bit set.
dnsrr_resolver.cc 109 : ttl(0), dnssec(false), negative(false) {
225 // For DNSSEC, a 4K buffer is suggested
281 response_.dnssec = false;
564 dnssec = false;
587 dnssec = true;
dnsrr_resolver_unittest.cc 183 ASSERT_FALSE(response.dnssec);
  /external/chromium/net/socket/
ssl_client_socket_nss.cc 314 // dnssec: if true then the TXT records are DNSSEC validated. In this case,
319 bool dnssec,
385 if (dnssec)
396 // CheckDNSSECChain tries to validate a DNSSEC chain embedded in
420 oid_data.desc = "DNSSEC chain";
442 LOG(ERROR) << "DNSSEC chain verification failed: " << err;
450 true /* DNSSEC verified */, server_cert_nss, verifier.rrdatas());
    [all...]
  /external/ipsec-tools/src/racoon/
cftoken.l 328 <S_RMTS>dnssec { YYD; return(DNSSEC); }

Completed in 36 milliseconds