summaryrefslogtreecommitdiffstats
path: root/lib/libc/include
diff options
context:
space:
mode:
authorpatrick <patrick@openbsd.org>2017-12-04 16:52:16 +0000
committerpatrick <patrick@openbsd.org>2017-12-04 16:52:16 +0000
commit453c4015b77f81e940e22e3ac42b969c85510b0c (patch)
tree6d154e51fd2425e58e4617c8a1be6389a59a8774 /lib/libc/include
parentRFC 4861 requires that all neighbor discovery packets have 255 in (diff)
downloadwireguard-openbsd-453c4015b77f81e940e22e3ac42b969c85510b0c.tar.xz
wireguard-openbsd-453c4015b77f81e940e22e3ac42b969c85510b0c.zip
The payloads are layered like onions, so you can validate one layer and
then call the next one, which can then validate itself. Thing is, most layers try to run validations on the upper layer, which is not useful and rather confusing. This cleans it up. First change is that the generic payload parser does not anymore pass the length of the whole datagram, including all remaining payloads, but passes only the length of the specific payload to the specific payload parser. Second change is that the payload validators don't check the length of the upper layer, but only verify their own lengths. Diff discussed with hshoexer@ and sthen@ Tested by sthen@
Diffstat (limited to 'lib/libc/include')
0 files changed, 0 insertions, 0 deletions