Log Message:
security/sudo: update to sudo-1.9.16

# noteworthy changes (since 1.9.16)

* Sudo 1.9.16p2
	Sudo now passes the terminal device number to the policy plugin even
	if it cannot resolve it to a path name. This allows sudo to run
	without warnings in a chroot jail when the terminal device files
	are not present. GitHub issue #421.

	On Linux systems, sudo will now attempt to use the symbolic links in
	/proc/self/fd/{0,1,2} when resolving the terminal device number.
	This can allow sudo to map a terminal device to its path name even
	when /dev/pts is not mounted in a chroot jail.

	Fixed compilation errors with gcc and clang in C23 mode. C23 no
	longer supports functions with unspecified arguments. GitHub issue
	#420.

* Sudo 1.9.16p1
	Fixed the test for cross-compiling when checking for C99 snprintf().
	The changes made to the test in sudo 1.9.16 resulted in a different
	problem. GitHub issue #386.

	Fixed the date used by the exit record in sudo-format log files.
	This was a regression introduced in sudo 1.9.16 and only affected
	file-based logs, not syslog. GitHub issue #405.

	Fixed the root cause of the “unable to find terminal name for
	device” message when running sudo on AIX when no terminal is
	present. In sudo 1.9.16 this was turned from a debug message into a
	warning. GitHub issue #408.

	When a duplicate alias is found in the sudoers file, the warning
	message now includes the file and line number of the previous
	definition.

	Added support for the --with-secure-path-value=no configure option
	to allow packagers to ship the default sudoers file with the secure
	path line commented out.

	Sudo no longer sends mail when a user runs sudo -nv or sudo -nl,
	even if mail_badpass or mail_always are set. Sudo already avoids
	logging to a file or syslog in this case