From: Ingo Schwarze <schwarze@usta.de>
To: discuss@mdocml.bsd.lv
Subject: mandoc-1.14.3 released (bugfixes only)
Date: Sat, 5 Aug 2017 16:29:00 +0200 [thread overview]
Message-ID: <20170805142900.GA59893@athene.usta.de> (raw)
Hi,
unfortunately, the mandoc-1.14.2 release contains two somewhat
inconvenient regressions that escaped testing. For that reason,
i just uploaded a quick follow-up release 1.14.3, which is a pure
bug fix release.
mandoc-1.14.3 fixes the following issues, with no other changes:
* man(7): Do not crash with out-of-bounds read access to a constant
array if .sp or a blank line immediately precedes .SS or .SH.
This regression caused crashes when compiled with hardening on
Linux. It is inconvenient because a number of real-world Linux
manual pages trigger it, including mount(8).
* mdoc(7): Do not crash with out-of-bounds read access to a constant
array if .sp or a blank line precede the first .Sh macro.
This is a minor bug, and no manual pages was found in the wild
to trigger it, but the fix is very similar to the fix of the
previous, more serious bug.
* tbl(7): Ignore explicitly specified negative column widths rather
than wrapping around to huge numbers and risking memory exhaustion.
This bug is somewhat inconvenient because negative column widths
can occur in practice when manual pages attempt to calculate
columns widths using special roff(7) number registers not supported
by mandoc(1). In particular, the Linux ps(1) manual page triggers
the bug.
* man(1): No longer use names that only occur in the SYNOPSIS section.
Gets rid of some surprising behaviour and bogus warnings.
This is a minor issue, but it was found to cause some confusion
with respect to a number of illumos manual pages.
Sorry for the inconvenience.
Please use mandoc-1.14.3 rather than mandoc-1.14.2.
Yours,
Ingo
--
To unsubscribe send an email to discuss+unsubscribe@mandoc.bsd.lv
reply other threads:[~2017-08-05 14:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170805142900.GA59893@athene.usta.de \
--to=schwarze@usta.de \
--cc=discuss@mandoc.bsd.lv \
--cc=discuss@mdocml.bsd.lv \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).