Lines Matching refs:assertion
8 4467. [security] It was possible to trigger a assertion when rendering
97 "none" ACL could cause an assertion failure in
100 4319. [security] Fix resolver assertion failure due to improper
394 4178. [bug] Fix assertion failure in parsing UNSPEC(103) RR from
397 4177. [bug] Fix assertion failure in parsing NSAP records from
418 rdatatype could trigger an assertion failure.
426 assertion failure when parsing certain malformed
432 result in an assertion failure. (CVE-2015-5477)
483 in an assertion failure. (CVE-2015-4620) [RT #39795]
557 cause an assertion in mem.c. [RT #38979]
688 to crash with an assertion failure.
712 4044. [bug] Change 3955 was not complete, resulting in an assertion
820 reference could be leaked causing an assertion
984 to a assertion failure. Also zero out new acl elements
1179 portentry could be reset leading to an assertion
1231 3770. [bug] "dig +trace" could fail with an assertion when it
1286 3737. [bug] 'rndc retransfer' could trigger a assertion failure
1673 trigger an assertion failure in resolver.c
1941 could trigger an assertion failure when used in
2013 3440. [bug] Reorder get_key_struct to not trigger a assertion when
2242 could trigger an assertion failure on startup.
2670 causing an assertion failure. [RT #26180]
2675 nonexistent records, leading to an assertion
2691 possible assertion failure. [RT #23219]
2698 overload could trigger an assertion failure. [RT #26463]
2801 cause an assertion failure on shutdown. [RT #26271]
2870 assertion failures. [RT #25880]
2990 RPZ to exit with a assertion failure. [RT #24766]
2993 RPZ caused named to exit with a assertion failure.
3003 crash with an assertion failure. [RT #24777]
3079 an assertion failure in named-checkconf. [RT #24382]
3883 could trigger an assertion failure. [RT #21133]
4251 2757. [bug] dig: assertion failure could occur in connect
4268 2750. [bug] dig: assertion failure could occur when a server
4585 2667. [func] Add support for logging stack backtrace on assertion
4724 2626. [bug] Multiple trusted-keys could trigger an assertion
4869 statistics channel, triggering an assertion failure in
5431 2415. [bug] 'rndc dumpdb' could trigger various assertion failures
5456 could then trigger an assertion failure in
5498 assertion in acl.c. [RT #18166]
5566 2370. [bug] "rndc freeze" could trigger an assertion in named
5583 2364. [bug] named could trigger a assertion when serving a
8538 space (which caused an assertion failure) in
8583 1372. [bug] named crashes with an assertion failure on exit when
9127 1182. [bug] The server could throw an assertion failure when
9329 could cause an assertion failure in resolver.c
9368 1107. [bug] nsupdate could catch an assertion failure if an
9378 could cause an assertion failure. [RT #1995]
9460 1076. [bug] A badly defined global key could trigger an assertion
9467 cause an assertion failure. [RT #1946]
9506 could catch an assertion failure. [RT #1912]
9521 1056. [bug] Rndc could catch an assertion failure on SIGINT due
9575 1041. [bug] Dig/host/nslookup could catch an assertion failure
9586 could cause an assertion failure. [RT #1866, #1869]
9679 an assertion failure. [RT #1766]
9688 an assertion failure could subsequently be triggered
9770 could trigger an assertion failure. [RT #1692]
9786 caused an assertion failure.
10322 cause an assertion failure. [RT #1218]
10351 could cause an assertion failure during load.
10429 an assertion failure. [RT #673, #872, #1048]
10434 783. [bug] Following CNAMEs could cause an assertion failure
10444 other rare errors could lead to assertion failures
10485 assertion when the server exited.
10561 assertion failure in the query code. [RT #881]
10579 with an assertion failure. [RT #852]
10610 an assertion failure. [RT #809]
10630 719. [bug] Rapid reloads could trigger an assertion failure.
10643 715. [bug] Resolving some A6 chains could cause an assertion
10653 assertion failure. [RT #718]
10703 696. [bug] lwresd would die with an assertion failure when passed
10718 691. [bug] Configuring per-view forwarders caused an assertion
10751 678. [bug] "transfer-format one-answer;" could trigger an assertion
10809 661. [bug] Certain UDP IXFR requests caused an assertion failure
10896 would cause an assertion. [RT #590]
10952 an assertion failure.
10967 to false positives, causing assertion failures.
11126 assertion failure. [RT #302]
11161 crash with an assertion failure on certain
11285 517. [bug] The resolver's DNAME code would trigger an assertion
11292 assertion. [RT #399]
11306 511. [bug] The message code could throw an assertion on an
11416 on failure. This caused assertion failures when
11590 424. [bug] notify_createmessage() could trigger an assertion
11633 411. [bug] A typo in the HS A code caused an assertion failure.
11659 warning and then later throwing an assertion.
11669 assertion failure trying to perform zone
11675 398. [bug] "dig" sometimes caught an assertion failure when
11709 support caused an assertion failure [RT #235].
11761 of a very large RRset could cause an assertion failure
11820 an assertion failure.
11849 triggering an assertion.
11873 zone triggered an assertion failure.
11891 causing assertion failures.
12004 assertion as it tried to cancel an already-canceled
12011 assertion failure trying to perform zone
12046 an assertion failure.
12099 message, causing an assertion to be triggered. Fixed.
12156 269. [bug] Failed DNSSEC validations could cause an assertion
12199 This manifested itself as assertion failures during the
12220 251. [bug] lwresd caught an assertion failure on startup.
12240 server to catch an assertion failure when it
12329 an assertion failure.
12348 could cause the assertion INSIST(client->lockview
12421 in a negative response caused an assertion
12459 (ie, something that could generate an assertion)
12641 cause an assertion failure.
12932 == 0 assertion in query_newname().
12944 could catch an assertion or lose signature data,
12997 not an SOA, the server died with an assertion failure
13082 db_rr_iterator_first(), possibly causing an assertion
13087 trigger an assertion.