Now that runc builds according to available kernel features and there
is no longer a sub-menu to select them manually, also drop the MENU:=1
statement from the package Makefile.
Fixes: 3a06ce559 ("runc: Updated to v1.0.0-rc92 for dockerd")
Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* adds the canon_lide70 backend
* avision: adds support for the KODAK i1120, fixes thread cancellation issues,
disables exposure option for non-filmscanners
* canon_dr: improves error reporting
* dmc: fixes compiler warnings on the scan area options
* epsonds: rewrites the network I/O following changes made to the
* epson2 backend in 1.0.30 to fix security issues. Network support is still
unsupported.
* fujitsu: adds support for the fi-800R and a card scanning slot, fixes a bug
when reading hardware sensors on the first invocation. Adds USB IDs for
fi-7800 and fi-7900.
* genesys: adds support for the Canon 5600F, Canon LiDE 90, Plustek OpticFilm
7200 and 7200 (v2), 7400, 7600i, 8100 and 8200i. Fixes several issues with the
Canon 8600F. Adds 4800dpi support for the Canon LiDE 210 and fixes 3200dpi
flatbed support on the Canon 8400F. Adds an option to fill dark calibration
with a constant. Adds transparency support for gl847 chipset based devices.
Fixes CIS scanner support for gl842 chipset based devices. Removes lineart and
image enhancement emulation support.
* gphoto: supports the PLANon DocuPen RC800 (with a recent enough version of
gphoto2)
* gt68xx: modifies scan cancellation behaviour
* hp5400: adds button support, fixes a scan cancellation crash issue
* pixma: add supports for the i-SENSYS MF440 Series and untested support for the
PIXMMA G7000 Series and GM4000 Series as well as the i-SENSYS MF720 Series.
* plustek: fixes a potential buffer overrun
* test: adds gamma options
Patches:
- ADD: 102-pixma_Restore_old_behaviour_in_case_XML_support_is_missing.patch:
pixma was failing to detect libxml2, even when it exists
(https://gitlab.com/sane-project/backends/-/issues/345)
- DROP: 100-fix-bigendian.patch: fix in release
Signed-off-by: Luiz Angelo Daros de Luca <luizluca@gmail.com>
It's nice to have seccomp support which is enabled in OpenWrt on
supported platforms on targets which are not marked as SMALL_FLASH.
(and it's kinda obvious that you wouldn't want to install runc on a
SMALL_FLASH target to begin with)
So let's enable seccomp by default.
Signed-off-by: Daniel Golle <daniel@makrotopia.org>
Better a separate package than enabling it via busybox.
Special thanks to @neheb for the Makefile patches.
Signed-off-by: Paul Spooren <mail@aparcar.org>
Installing the 'xz' package currently leads to file collisions:
Collected errors:
* check_data_file_clashes: Package xz wants to install file /usr/bin/unxz
But that file is already provided by package * busybox
* check_data_file_clashes: Package xz wants to install file /usr/bin/xz
But that file is already provided by package * busybox
* opkg_install_cmd: Cannot install package debootstrap.
Fix that by switching to use ALTERNATIVES for all multicall commands
instead of copying the symlinks into the package.
Signed-off-by: Daniel Golle <daniel@makrotopia.org>
dirmngr is needed to download keys from keyservers.
That being a useful thing, let's package dirmngr.
Signed-off-by: Daniel Golle <daniel@makrotopia.org>
Ship podman with defaults more coherent with user expectations and
more likely to work out-of-the-box.
Signed-off-by: Daniel Golle <daniel@makrotopia.org>
Deleting rules that docker has created is error-prone, because with
every update docker we have to check if anything has changed.
Cleaning up the firewall rules is part of the docker and should and must be
cleaned up and handeled by them when the service is terminated.
Signed-off-by: Florian Eckert <fe@dev.tdt.de>
If docker-ce handles the firewall and fw3 is not envolved because the
rules get not proceed, then not only docker0 should be handled but also
other interfaces and therefore other docker networks.
This commit extends the handling and introduces a new uci option
`device` in the docker config firewall section. This can be used to specify
which device is allowed to access the container. Up to now only docker0
is covert.
Signed-off-by: Florian Eckert <fe@dev.tdt.de>
As the protocol is set to none, this makes no sense here, as it cannot
be controlled and thus processed by the netifd.
Signed-off-by: Florian Eckert <fe@dev.tdt.de>
Openwrt has a own firewall service called fw3, that supports firewall zones.
Docker can bypass the handling of the zone rules in openwrt via custom
tables. These are "always" processed before the openwrt firewall.
Which is prone to errors!
Since not everyone is aware that the firewall of openwrt will
not be passed. And this is a security problem because a mapped port is
visible on all interfaces and so also on the WAN side.
If the firewall handling in docker is switched off, then the port in
fw3 must be explicitly released and it cannot happen that the
port is accidentally exported to the outside world via the interfaces on
the WAN zone.
So all rules for the containers should and so must be made in fw3.
Signed-off-by: Florian Eckert <fe@dev.tdt.de>
Up to now only the docker0 interface and bridge is created by default.
In order to create other interfaces and to integrate them into the
openwrt these functions can now be called with arguments.
Signed-off-by: Florian Eckert <fe@dev.tdt.de>
* blocked_interfaces blocks all packets to docker0 from the given
interface. This is needed because all the iptables commands dockerd
adds operate before any of the fw3 generated rules.
Signed-off-by: Gerard Ryan <G.M0N3Y.2503@gmail.com>
