fix off-by-one in checking hostname length in new resolver backend
authorRich Felker <dalias@aerifal.cx>
Mon, 2 Jun 2014 05:31:28 +0000 (01:31 -0400)
committerRich Felker <dalias@aerifal.cx>
Mon, 2 Jun 2014 05:31:28 +0000 (01:31 -0400)
commitbb9af59bba5b72b90c38d28809c30b31933c64d5
tree733606f802ae0cf39895d1073839820eb0b92116
parentaf7c308ee66c4127700dd7843f885f7f2d030a0c
fix off-by-one in checking hostname length in new resolver backend

this bug was introduced in the recent resolver overhaul commits. it
likely had visible symptoms. these were probably limited to wrongly
accepting truncated versions of over-long names (vs rejecting them),
as opposed to stack-based overflows or anything more severe, but no
extensive checks were made. there have been no releases where this bug
was present.
src/network/lookup_name.c