replaced by mox-a53-firmware in 72919fc3

For now, there is a bug in Chromium-based browsers
that fails on HTTPS + WSS connection for no reason:
https://bugs.chromium.org/p/chromium/issues/detail?id=1346579.

This fix will allow users to get through the onboarding wizard.

Fixed downloading firmware and image regeneration.

See https://gitlab.nic.cz/turris/turris-netboot/-/tags/v0.7.1

Mainly use sudo to get access to the wireless configuration even as an
ordinary user.

Release notes:
- https://gitlab.nic.cz/turris/turris-netboot/-/tags/v0.7.0

Updated copyright

uboot is now built directly from upstream, the package name is
mox-uboot-uboot and it's build only, so users can not install this
package. It's used to build a new package called mox-a53-firmware that
combines uboot with trusted firmware and provides the uboot-devel binary
like uboot-mox used to.

Changelog:
https://redmine.lighttpd.net/versions/68

- It fixes Ubi offset header

reForis Changelog:
* Add & update translations
* Fix client-relative session expiration
* NPM audit fix

Ok, it seems that it was happening also in the HBS (before my fix as it
does not get into release), thus we can be sure
that I did not break it, thus revert it once again.

This reverts commit 64045edc.

Even though, the previous solution fixes this output:
```
cmp: /boot/boot.scr: No such file or directory
cp: can't stat '/boot/boot.scr': No such file or directory
```

It seems there is some issue with infinite loop of symlinks
```
INFO:Executing postupdate hook: 10_kernel-install
//boot/zImage /tmp/tmp.NEAjjh/zImage differ: char 5, line 1
cmp: //boot/fdt: Symbolic link loop
cp: can't stat '//boot/fdt': Symbolic link loop
```

Because of that, revert it for now as we would like to release a new
version soon.

This reverts commit e68eda1d.

Fixes:
- CVE-2022-30698
- CVE-2022-30699

Release notes:
https://nlnetlabs.nl/projects/unbound/download/#unbound-1-16-2

HBK version of the same fix already applied to HBL. Original
description:

Make sure that sessions use relative time from browser, so you can setup
your router even if your router/browser has a wrong time. Big thanks and
the credits go to László Várady.

Make sure that sessions use relative time from browser, so you can setup
your router even if your router/browser has a wrong time. Big thanks and
the credits go to László Várady.

Josef Schlehofer authored 2 years ago and Michal Vasilek committed 2 years ago

The file boot.scr should be in boot folder and not in root,
because then it is not in the same way as it is done for Turris Omnia
and Turris MOX. I checked it with Turris OS 3.x release also, when
boot.scr was introduced for Turris 1.x routers and there is also in boot
folder.

Fixes the following output:
cmp: /boot/boot.scr: No such file or directory
cp: can't stat '/boot/boot.scr': No such file or directory

Fixes: 03c8a7c7 ("turris1x-btrfs: deploy
boot.scr and link the appropriate dtb name")

Remove backported patches, which was taken from this tagged release:

* Fixed case when updates were installed automatically, even though manual confirmation was required.
* Fix detection of delayed reboot and thus create complete notification for it.

Fixed:
- notifier: Add timezone to timestamp in email notification
(remove the patch, which backported the change)

This patch is already merged to user-notify repository, but until there
is tagged release, let's do it this way.

We provided two servers for reForis - flup and cgi. Unfortunately, no
one uses cgi and it is not documented how to use it. Let's drop it.

Josef Schlehofer authored 2 years ago and Michal Vasilek committed 2 years ago

This helps in cases when someone forgets to bump PKG_RELEASE.

Reference:
https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=9ae3c6f94c616cfbf854d3ec749c7fafc9893942

File resolv.conf.auto is now stored mainly in the directory
/tmp/resolv.conf.d as well as resolv.conf files generated by OpenVPN
client, so let's prefer this directory for reading nameservers. It is
more secure.

File resolv.conf.auto is now stored mainly in the directory
/tmp/resolv.conf.d as well as resolv.conf files generated by OpenVPN
client, so let's prefer this directory for reading nameservers. It is
more secure.

Use new /tmp/resolv.cond.d directory to store nameservers provided by
OpenVPN. It is more secure and new default in OpenWrt:

https://github.com/openwrt/openwrt/commit/cd48d8d3420dd4df03daaa548227ceb487ba7104

1. initrd.gz: ASCII cpio archive (SVR4 with no CRC)
Replace it by ugly cp instead of renaming it in two packages

This is the upstream change in Linux Kernel Build repository.
Refer: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/usr/Makefile?h=v5.10.74&id=80e715a06c2d0a24dbb818bb1dba2ef0f20d7068

It was changed that the MOX is now the same as Turris Omnia

This is the upstream change in Linux Kernel Build repository.
Refer: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/usr/Makefile?h=v5.10.74&id=80e715a06c2d0a24dbb818bb1dba2ef0f20d7068

This is required becase of changes done in Turris Build repository.
The previous target was not good to upstream it to OpenWrt. This helps a
little bit to be in sync how the Turris Omnia and Turris MOX are done

Release notes:
https://www.nlnetlabs.nl/news/2022/Jul/11/unbound-1.16.1-released/