We prepared for you a new version of Turris OS 5.1.4, which you can now find in the Testing branch.
What’s has been changed in this release?
There are improvements updated DNS rules based on DNS Flag Day 2020. Default EDNS buffer size is now 1232 bytes. This means updated packages for DNS resolvers - Unbound, Knot Resolver.
If you are using Nextcloud, we updated mariadb due to security vulnerabilities. Also, there are security fixes for php7.
You can find updated netmetr package and we updated package for diagnostics, where we improvement updater module.
How to test this release before it gets to the stable branch?
If you are using the HBT branch since earlier posts, you don’t need to do anything.
If you want to be part of our testing community, you need to use SSH and connect to your router. After logging in, freel free to proceed with following command, which takes you to the Testing branch.
switch-branch hbt
If you decide anytime to opt out from testing branch, you need to replace hbt with hbs according to our documentation.
- Cosmetic issue:
Mismatch of different Turris OS versions in /etc/turris-version and /etc/openwrt_release.
This is caused that package base-files was not updated. This package is versioned as you can see here by using two variables PKG_RELEASE and VERSION. PKG_RELEASE is stated in Makefile, but REVISION comes from commit hash of openwrt-19.07 branch. This was not changed during 5.1.3 and 5.1.4 RC1. You can compare it on repo.turris.cz, where you go to HBS and HBT folders and check git-hash file.
Guys, in the Czech Republic, and also it depends on your timezone, we are releasing on 13th Friday the new RC version of Turris OS 5.1.4.
What has been changed?
Kernel version was updated to version 4.14.206. This version is not in OpenWrt 19.07 so far, but it is in OpenWrt 18.06.
It fixes security vulnerability Sad DNS. (Czech version here)
More details can be found here: https://gitlab.nic.cz/turris/turris-build/-/issues/206
We haven’t done anything about the reboot issue in this release and we are already aware of it and our kernel development team introduced a workaround that might help in some case, but it requires some knowledge to follow steps to try it. Unfortunately, we don’t know, why it does not work in your case, but please let’s leave this discussion elsewhere than here. You could use one of the threads, which are created on forum like this one Turris Mox powers down - #21 by mbehun - MOX hardware - Turris forum.