| Age | Commit message (Collapse) | Author |
|---|
|
|
|
conditional request on the same input line, don't skip the first few
bytes of its content.
|
|
response's content length may be an unexpected value as an error
page is shown.
|
|
Replace -y with -S (supported by GNU and FreeBSD sorts).
|
|
write to trigger connection close, allow errors EPIPE or ECONNRESET.
|
|
when it receives a SIGHUP.
|
|
without the required subsequent argument; found by jsg@ with afl.
|
|
subscripts, superscripts, or "from" or "to" arguments.
Found by jsg@ with afl.
|
|
|
|
|
|
in mandoc(1). So practice some recursive programming to make sure
it doesn't get broken.
|
|
|
|
logging of SSL errors. Do not import unneeded Socket constants.
|
|
ending!) the definition of another user defined macro.
Mandoc already handles this correctly, make sure it won't get broken.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
rsyslogd from ports. If the rsyslog package is installed, rsyslogd
is used as drain to test interoperability. This will be especially
useful for syslog via TCP and TLS.
|
|
for openssl(1), which is also variable in behaviour between applications
(and currently inconsistent).
|
|
Not exactly recommended for use, rather for groff compatibility.
While here, introduce similar SHRT_MAX limits as in man(7),
fixing a few cases of infinite output found by jsg@ with afl.
|
|
because negative indents can get truncated, in which case we no longer
know how to restore the original indent at the end of the block.
This also solves another case of effectively infinite output found
by jsg@ with afl, triggered by very large negative indents.
|
|
for a table cell with an "nz" layout specification,
causing essentially infinite output as found by jsg@ with afl.
|
|
minus twenty lines of code in spite of enhanced functionality
|
|
- .sp with an invalid argument is .sp 1v, not .sp 0v
- in man(1), trailing garbage doesn't make scaling units invalid
|
|
|
|
Basic units, centimeters, points, ens, ems, and the rounding algorithm
were all wrong, only inches, pica, and the default vertical span worked.
|
|
|
|
Similarly, avoid having the same block break two other blocks.
In some situations, this could lead to an endless loop in rew_sub()
found by jsg@ with afl.
Minimal example: .Po Ao Pc Bo Pc Ac Bc
|
|
ok markus@
|
|
|
|
fingerprint format
|
|
fix it by ensuring more stdio fds are sent to devnull
|
|
1) rew_sub(): Make sure REWIND_MORE is acted upon even when followed by
REWIND_NONE. This prevents .It from ending up inside other children of .Bl.
2) blk_exp_close(): Only allow extension of .Bl when it has at least
one .It. Otherwise, a broken child block could be moved in front of
the .Bl, effectively resulting in a .Bl that ended before it began.
|
|
makes the fragment tests work on FreeBSD. From Ilya Bakulin.
|
|
It accepted invalid byte sequences like 0xc080-c1bf, 0xe08080-e09fbf,
0xeda080-edbfbf, and 0xf0808080-f08fbfbf, produced valid roff Unicode
escape sequences from them, and the algorithm contained strong
defenses against any attempt to fix it.
This cures an assertion failure in the terminal formatter caused
by sneaking in ASCII 0x08 (backspace) by "encoding" it as an (invalid)
multibyte UTF-8 sequence, found by jsg@ with afl.
As a bonus, the new algorithm also reduces the code in the function
by about 20%.
|
|
|
|
Fixes an assertion found by jsg@ with afl.
|
|
the first .It. Otherwise, move it out together with whatever
follows. Fixing an assertion failure found by jsg@ with afl.
|
|
macro (for example .Xo) and never closed again, the item ends up
without a body block. This can even happen for list types that
usually don't have heads in the first place. So even in this
case, check for the existence of the body before accessing it.
NULL pointer access found by jsg@ with afl.
|
|
Found by jsg@ with afl.
|
|
already closed. In this respect, also consider lists closed
that have broken another block, their closure pending until the
end of the broken block. This avoids syntax tree corruption
leading to a NULL pointer access found by jsg@ with afl.
|
|
|
|
would abort the table in an unclean way, causing assertion failures
found by jsg@.
|
|
and change the name of \(-~ to \(|= to agree with groff;
difference found by Carsten dot Kunze at arcor dot de
|
|
just like explicit block macros themselves.
Fixing an assertion failure jsg@ found with afl.
|
|
character of input, treat it as false, do not retry it as a string
comparison condition. This also fixes a read buffer overrun that
happened when the numerical condition advanced to the end of the
input line before erroring out, found by jsg@ with afl.
|
