Browser integration only works with Chromium-based browsers
and/or Firefox, build it only on archs that support either of
these two to avoid wasting bulk time.
"fine for me" rsadowski@ (maintainer), OK kmos@
Make shells(5) list it and enable "chsh -s git-shell user";
"chsh -s /usr/local/bin/git-shell user" already works but is more typing
and inconsistent with other shells.
* fix endless loop on platforms where char is unsigned, e.g. macppc
(fix by Klemens Nanni)
* print interface v6 address on -vv
* fix log message if no suitable address could be picked
All patches upstreamed, thanks Tim Kuijsten (author/maintainer)!
* Fix IsAncestor and IsDescendant when the same page is passed
* deps: Update goldmark-highlighting
* Fix IsAncestor and IsDescendant under subsection
ok jca@
Python" messages, Python 2 development has finished so this is not a
sensible option to use as default.
(It is still kept in the ports tree for now, as some important software
has not been updated to use Python 3).
ok tracey aja mariani rpointel
From https://www.python.org/doc/sunset-python-2/, "We are volunteers who
make and take care of the Python programming language. We have decided
that January 1, 2020, was the day that we sunset Python 2. That means
that we will not improve it anymore after that day, even if someone
finds a security problem in it. You should upgrade to Python 3 as soon
as you can."
Without documentation and/or prior Ruby experience, it is not obvious
what /etc/ruby-version should contain.
The shim script itself should not be called directly, move it to
libexec/rubyshim to make this clearer.
by specifying "-std=gnu99" and patching to remove "-Werror"
Input from aja
ok jca@
(Last commit was mistakenly done from within "patches", thus missing
Makefile)
Wear-leveled SPI flash file system for embedded devices.
This tool is specifically patched to build and unpack SPIFFS images for
esp32 and esp8266 wifi devices, using SPIFFS as the submodule.
Testing paco@
Input from jca@ and sthen@
Ok benoit@ paco@ kmos@ sthen@ jca@
SQUID-2020:3 - Due to incorrect buffer handling Squid is vulnerable to
cache poisoning, remote execution, and denial of service attacks when
processing ESI responses.
SQUID-2020:4 - Due to an integer overflow bug Squid is vulnerable to
credential replay and remote code execution attacks against HTTP Digest
Authentication tokens.
