If eqn(7) or tbl(7) input is encountered in -mdoc -T markdown mode,
print a line describung the problem to the formatted output and also
raise an "unsupp" message, similar to what -T man already does,
instead of calling assert(3), which is never appropriate when dealing
with unsopported or incorrect input.
A conversation with kristaps@ reminded me of this issue.
Check for unsigned integer overflow when calculating how much beyond
our local window a peer has sent. Prevents them sneaking past the grace
we allow.
bz#4031, from rhowe425 at gmail.com, ok markus@
Remove the SSH_OLD_SESSIONID bug compatibility bit. It was only
set for SecureCRT 3.0 and SecureFX 1.7. Both date back to some
time prior to 2002 (vandyke's release history only goes back to
2002, and these releases predate that).
Prompted by rhowe425 at gmail.com via bz#4030, ok markus@
remove angr and angrop for now; this angr versiom isn't working with
python 3.14 and I haven't been able to figure out how to build new
versions. (a new major version has recently come out and might be worth
another attempt maybe when it's settled down a bit, but it looks like
some of the deps currently in devel/angr/xxx are no longer used so that
is probably worth redoing the set).
prompted by build failure after updating py-cparser reported by naddy,
but I noticed that it had already been failing at runtime for a while.
tb looked at trying to fix too.
ok jasper (maintainer)
tweak previous: drop stray blank line, drop a few words that accidentally
stayed behind, and fix some plural->singular issues;
feedback and OK mglocker@, and OK jca@ on an earlier version
Create the weak global _permit_setugid which must match the setuid/setgid
mode of the executable file. This is documented in execve(2).
The libc startup validation code to do this is not enabled yet.
xlock is setgid (auth), but does not use the bsd.prog.mk build infrastructure,
so it needs manual definition of "mode_t _permit_setugid = S_ISGID". The other
setgid program in X11R6 is xterm (group utmp), but it is built using bsd.prog.mk
and automatically picks up the _permit_setugid variable.
Update libexpat to version 2.8.5.
Changes relevant for OpenBSD have been backported earlier. Compiler
warning #1362 has been disabled, it does not work with gcc 4.2.1.
Move the hash table declarations into a separate header file as
this is needed for #1355. Convert salt test to non deprecated
XML_SetHashSalt16Bytes() function. Library bump is not necessary.
OK deraadt@
update to py3-dulwich-1.2.17
make a start at trying to allow rust/no-rust builds, but I'm not sure if
there's a good way to add SUPDISTFILES for the crates..