On Thu, Apr 13, 2017 at 07:56:39AM +0100, Iain Hibbert wrote:
> On Thu, 13 Apr 2017, Brooks Davis wrote:
>
> > I've found a one byte buffer overflow in t_vis.c. It's caused by a
> > quite reasonable confusion about an undocumented behavior of always add
> > a
On 04/13, Brooks Davis wrote:
> diff --git a/contrib/netbsd-tests/lib/libc/gen/t_vis.c
> b/contrib/netbsd-tests/lib/libc/gen/t_vis.c
> index adb0930a300..9b9501d5b9c 100644
> --- a/contrib/netbsd-tests/lib/libc/gen/t_vis.c
> +++ b/contrib/netbsd-tests/lib/libc/gen/t_vis.c
> @@ -68,7 +68,12 @@ ATF_
On Thu, 13 Apr 2017, Brooks Davis wrote:
> I've found a one byte buffer overflow in t_vis.c. It's caused by a
> quite reasonable confusion about an undocumented behavior of always add
> a '\0' terminating the dst string in strnunvisx(). This patch fixes the
> t
I've found a one byte buffer overflow in t_vis.c. It's caused by a
quite reasonable confusion about an undocumented behavior of always add
a '\0' terminating the dst string in strnunvisx(). This patch fixes the
test, but I think the behavior is confusing and should be docum
