NetBSD/lib/libutil
dyoung bfa27930cb In sockaddr_snprintf(sbuf, len, fmt, sa), do not write the terminating
null character outside of the byte region [sbuf, sbuf + len).

1) If the length of the buffer is 0, do not write a null character
   at all.  Previously, sockaddr_snprintf() may have been able to
   overwrite sbuf[-1] if len was 0.

2) If the length of the buffer, len, is greater than 0, then write
   the null at sbuf[len - 1].  Previously, sockaddr_snprintf()
   wrote the null at buf[len - 1], where `buf' was a "cursor" that
   did not necessarily equal `sbuf', the start of the buffer.  Now,
   sockaddr_snprintf() always writes the null at sbuf[len - 1].
2007-07-24 08:45:45 +00:00
..
Makefile
disklabel_dkcksum.3
disklabel_dkcksum.c
disklabel_scan.3
disklabel_scan.c
efun.3
efun.c
getbootfile.3
getbootfile.c
getlabelsector.3
getlabelsector.c
getmaxpartitions.3
getmaxpartitions.c
getmntopts.3
getmntopts.c
getrawpartition.3
getrawpartition.c
if_media.c
login.3
login.c
login_cap.3
login_cap.c
login_tty.c
loginx.3
loginx.c
logout.c
logoutx.c
logwtmp.c
logwtmpx.c
opendisk.3
opendisk.c
openpty.3
parsedate.3
parsedate.y
passwd.c
pidfile.3
pidfile.c
pidlock.3
pidlock.c
pty.c
pw_getconf.3
pw_init.3
pw_lock.3
pw_policy.3
pw_policy.c
secure_path.3
secure_path.c
shlib_version
snprintb.3
snprintb.c
sockaddr_snprintf.3
sockaddr_snprintf.c In sockaddr_snprintf(sbuf, len, fmt, sa), do not write the terminating 2007-07-24 08:45:45 +00:00
stat_flags.3
stat_flags.c
ttyaction.3
ttyaction.c
ttymsg.3
ttymsg.c
util.3