]> git.ipfire.org Git - thirdparty/knot-resolver.git/commit
projects / thirdparty / knot-resolver.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 3e67230) | patch
cache: avoid potential out-of-bounds with NSEC3 params
authorVladimír Čunát <vladimir.cunat@nic.cz>
Fri, 15 Jun 2018 09:05:40 +0000 (11:05 +0200)
committerVladimír Čunát <vladimir.cunat@nic.cz>
Fri, 15 Jun 2018 09:16:13 +0000 (11:16 +0200)
commit703c21cb8b3e02c8d253545205379474efdd7085
treebb26d228f06c6e77dcdde628aa5c849cc51897a5tree | snapshot
parent3e6723044295df432335419db81846f6ed813a21commit | diff
cache: avoid potential out-of-bounds with NSEC3 params

It's possible the parser wouldn't let such RR through,
and it's most likely validator shouldn't let them through.
Even so, I feel better to check anyway.
lib/cache/api.c diff | blob | blame | history
lib/cache/impl.h diff | blob | blame | history
Mirror of https://gitlab.nic.cz/knot/knot-resolver.git