HomeSort by: relevance | last modified time | path
    Searched defs:published (Results 1 - 6 of 6) sorted by relevancy

  /src/external/mpl/bind/dist/bin/tests/system/ksr/
tests_ksr.py 132 # published: dnskey-ttl + publish-safety + propagation
133 published = active - timedelta(hours=2, minutes=5) variable
154 if retired is None or between(now, published, retired):
156 pubdelay = published + timedelta(hours=2, minutes=5)
159 if between(now, published, pubdelay):
189 assert f"Published: {published}" in metadata
283 published = key.get_timing("Publish")
284 if between(published, inception, next_bundle):
285 next_bundle = published
365 published = key.get_timing("Publish") variable
391 published = key.get_timing("Publish") variable
437 published = key.get_timing("SyncPublish") variable
488 published = key.get_timing("SyncPublish") variable
    [all...]
  /src/external/mpl/bind/dist/bin/dnssec/
dnssec-ksr.c 773 bool published = true; local
791 published = false;
794 published = false;
797 if (published) {
815 published = true;
828 published = false;
831 published = false;
834 published = false;
837 if (!published) {
  /src/external/mpl/dhcp/bind/dist/lib/dns/
keymgr.c 147 isc_stdtime_t published, syncpublish; local
154 ret = dst_key_gettime(key->key, DST_TIME_PUBLISH, &published);
164 syncpublish = published + dst_key_getttl(key->key) +
170 zrrsig_present = published + dns_kasp_zonemaxttl(kasp) +
184 * 2. If there is no published time set, also super weird, set it now.
190 * This returns when the successor key needs to be published in the zone.
651 * Key x is currently published and is going to be replaced by y. The
1078 * If no DNSKEYs are published, the state of the signatures is
1079 * irrelevant. In case a DNSKEY is published however, there
1329 * RFC 7583: The successor DS record is published i
    [all...]
zone.c 20724 "checkds: %u DS published "
20748 dspublish ? "published" : "withdrawn", dst_key_id(key));
20896 isc_stdtime_t published = 0, withdrawn = 0; local
20907 (void)dst_key_gettime(key->key, DST_TIME_DSPUBLISH, &published);
20910 if (ds_state == DST_KEY_STATE_RUMOURED && published == 0) {
20958 /* DS Published. */
21372 isc_stdtime_t published = 0, withdrawn = 0; local
21382 (void)dst_key_gettime(key->key, DST_TIME_DSPUBLISH, &published);
21385 if (ds_state == DST_KEY_STATE_RUMOURED && published == 0) {
21664 * published and is used for signing
    [all...]
  /src/external/mpl/bind/dist/lib/dns/
keymgr.c 165 isc_stdtime_t published, syncpublish; local
171 ret = dst_key_gettime(key, DST_TIME_PUBLISH, &published);
181 syncpublish = published + dst_key_getttl(key) +
188 zrrsig_present = published + ttlsig +
208 * 2. If there is no published time set, also super weird, set it now.
214 * This returns when the successor key needs to be published in the zone.
760 * Key x is currently published and is going to be replaced by y. The
1187 * If no DNSKEYs are published, the state of the signatures is
1188 * irrelevant. In case a DNSKEY is published however, there
1457 * RFC 7583: The successor DS record is published i
2896 isc_stdtime_t active = 0, published = 0, inactive = 0, local
    [all...]
zone.c 21071 "checkds: %u DS published "
21095 dspublish ? "published" : "withdrawn", dst_key_id(key));
21252 isc_stdtime_t published = 0, withdrawn = 0; local
21263 (void)dst_key_gettime(key->key, DST_TIME_DSPUBLISH, &published);
21266 if (ds_state == DST_KEY_STATE_RUMOURED && published == 0) {
21314 /* DS Published. */
22163 isc_stdtime_t published = 0, withdrawn = 0; local
22173 (void)dst_key_gettime(key->key, DST_TIME_DSPUBLISH, &published);
22176 if (ds_state == DST_KEY_STATE_RUMOURED && published == 0) {
22813 * published and is used for signing
    [all...]

Completed in 71 milliseconds