disabled.
This allows users to avoid mounting an extra FS that we don't enable by default.
Only display pkg-message with fdescfs instructions when option is enabled.
Submitted by: swills
Differential Revision: https://reviews.freebsd.org/D10394
with the real value of LOCALBASE by the port Makefile at some point, but it
isn't at the moment.
Set this value in the Makefile by defining CPPFLAGS accordingly.
PR: 217451
Submitted by: Dan McGregor <dan.mcgregor@usask.ca>
MFH: 2017Q1 (blanket)
(e.g. systems with an encrypted root partition) where it is impossible for the
fdescfs module to be autoloaded when /boot/kernel isn't available yet. Change
pkg-message accordingly.
Also change 'fdesc' mount point name to 'fdescfs' to simplify things: this way
'mount fdescfs' will work just as fine as 'umount fdescfs'. The less things to
remember - the better it is.
PR: 216985
Submitted by: John Smith <godevilove@ya.ru>
Changelog:
Fixes a bug. When -N is used, the input is not supposed to be split
using $IFS, but leading and trailing IFS whitespace was still removed.
MFH: 2017Q1
Changelog:
Under certain circumstances, bash will evaluate arithmetic expressions as
part of reading an expression token even when evaluation is suppressed. This
happens while evaluating a conditional expression and skipping over the
failed branch of the expression.
There is a race condition in add_history() that can be triggered by a fatal
signal arriving between the time the history length is updated and the time
the history list update is completed. A later attempt to reference an
invalid history entry can cause a crash.
Depending on compiler optimizations and behavior, the `read' builtin may not
save partial input when a timeout occurs.
Subshells begun to run command and process substitutions may attempt to
set the terminal's process group to an incorrect value if they receive
a fatal signal. This depends on the behavior of the process that starts
the shell.
MFH: 2017Q1
Changelog:
- Out-of-range negative offsets to popd can cause the shell to crash attempting
to free an invalid memory block.
- When performing filename completion, bash dequotes the directory name being
completed, which can result in match failures and potential unwanted
expansion.
MFH: 2017Q1
The reason is that NLS is related to message translations to different
languages.
And bash has the general feature that \uNNNN is translated into the unicode
character using iconv. This is unicode support, and should have nothing to
do with translations.
bash also currently has a bug that --disable-nls causes it to fail to find
iconv. This bug has been reported upstream to bash-devel ML. In the future,
when bash will fix this, this will make a difference.
Note that this uses iconv from libc.
[2] Update to 4.3.46
PR: 206903 [1], 210620 [2]
Submitted by: yuri@rawbw.com [1], pkubaj@anongoth.pl [2]
Discussed with: adamw
generate a bunch of,
cannot make pipe for process substitution: File exists
errors.
The problem lies with colliding pipe names.
The code in sh_mktmpname() in lib/sh/tmpfile.c uses a combination of things like
the current time, the PID, and an incrementing counter. Since the child PIDs
tend to be sequential (barring kern.randompid=1), there are collisions.
Fix this problem without rewriting upstream code by defining USE_MKTEMP=1 to
use the mktemp(3) code of bash.
FreeBSD's mktemp() is not nearly as bad as the bash default and isn't
brain-damaged like some platforms (which is likely why the bash code tries to
do it's own thing). In FreeBSD, "mktemp(3)" it uses arc4random to pick one of
62 symbols for each "X".
Submitted by: Henric Jungheim <software@henric.org>
When appropriate:
- Try to use DISTVERSION{SUF,PRE}FIX
- Replace PORTNAME-PORTVERSION by DISTNAME
- Convert MASTER_SITES to use macros
- Other light cleanup
With hat: portmgr
Sponsored by: Absolight
and reinstall. This should make the shells link with libintl.so.8 instead
of libintl.so.9 and should give package users a better chance of having a
working shell when something went wrong with the gettext update.
This addresses the local crash from CVE-2014-6277. Note that
the fixes applied in 4.3.25_2 (and upstream 4.3.27) already made
this non-exploitable remotely.
This makes 'bashcheck' [1] fully green now. It had a soft warning
before for CVE-2014-6277.
[1] https://github.com/hannob/bashcheck
This should eliminate the recent vulnerabilities, but keep the
requirement for --import-functions/IMPORTFUNCTIONS option for now.
- Loosen the --import-functions requirement so it is not needed when running
an interactive shell. It is already disallowed for privileged/setuid mode.
- Show an error on stderr when an imported function is ignored.
enabled by using --import-functions or enabling the IMPORTFUNCTIONS option.
This removes the risk of further parser bugs leading to code execution, as
well as the risk to setuid scripts and poorly written applications that
do not cleanse their environment [1][2].
Also note that there is an unofficial 4.3.26 floating around that has not yet
been officially released. r369261 covers the change in 4.3.26.
See also:
http://seclists.org/oss-sec/2014/q3/747 [1]
http://seclists.org/oss-sec/2014/q3/746 [2]
http://seclists.org/oss-sec/2014/q3/755 [3]
Obtained from: NetBSD (based on) [3]
PR: 193932
Reviewed by: Eric Vangyzen
With hat: portmgr
Since FreeBSD 8.4 and FreeBSD 9.1 make(1) do support :tu and :tl as a
replacement for :U and :L (which has been marked as deprecated)
bmake which is the default on FreeBSD 10+ only support by default
:tu/:tl a hack has been added at the time to support :U and :L to ease
migration. This hack is now not necessary anymore
Note that this makes the ports tree incompatible with make(1) from
FreeBSD 8.3 or earlier
With hat: portmgr
that we're at version "4.3.". Set PORTVERSION to 4.3.${PATCHLEVEL} until we have
the first patch released upstream. Also bump PORTREVISION to make sure all port
tools deal with this correctly.
Notified by: "Matthew D. Fuller" <fullermd@over-yonder.net>
Discussed with: kwm
