man-db 2.7.6
Milestone information
- Active:
- Yes. Drivers can target bugs and blueprints to this milestone.
Activities
- Assigned to you:
- No blueprints or bugs assigned to you.
- Assignees:
- No users assigned to blueprints and bugs.
- Blueprints:
- No blueprints are targeted to this milestone.
- Bugs:
- No bugs are targeted to this milestone.
Download files for this release
Release notes
Fixes:
------
o Fix build warnings with Perl 5.22.
o Document that 'man -K' searches page source, not rendered text.
o Fix a long-standing bug in man-db's internal cleanup stack
mechanism: if a cleanup function was pushed unexpectedly between a
push/pop pair, then popping the stack would remove the wrong
cleanup function and chaos could ensue. Avoid this by being more
precise about which cleanup function should be popped.
o SECURITY: Eliminate dangerous setgid-root directories. In the
default configuration, cache files and directories are now owned
by man:man rather than man:root; man and mandb are now setgid man
as well as setuid man (except in the --disable-setuid case). This
is a much simpler and safer solution to the original problem that
caused my predecessor to make directories setgid root, and doesn't
introduce any interesting new privilege since the man group's only
real purpose is to be the man user's primary group and nothing in
cache directories is group-writeable.
Maintainers of distribution packagers should take care to review
their installation rules in light of this change.
As far as I know this has no CVE ID, but it is described here:
http://
o Fix manual page translation infrastructure to render tables
correctly with po4a 0.47.
Improvements:
-------------
o man now understands the <page>.<section> form on its command line,
so for example 'man chmod.2' is now the same as 'man 2 chmod'.
(Contributed by Mihail Konev.)
o The owner of cache files is now configured separately from whether
man and mandb are installed setuid, using the
--enable-
Changelog
This release does not have a changelog.
0 blueprints and 0 bugs targeted
There are no feature specifications or bug tasks targeted to this milestone. The project's maintainer, driver, or bug supervisor can target specifications and bug tasks to this milestone to track the things that are expected to be completed for the release.