Turris OS 7.0.1 is now released!

Dear Turris users,

We just released Turris OS 7.0.1. Nothing groundbreaking in there, several small updates, the only thing that stands out is OpenSSH security update.

Changelog is as follows:

:pushpin: Updates
• openssh: Update to 9.8p1 (Security update)
• ethtool: Update to 6.6
• iproute2: Update to 6.7.0
• cronie: Update to 1.7.2
• schnapps: Update to 2.13.1 - support for Turris 1.x

:bug: Bug Fixes
• transmission: Downgrade to version 3 as new version seems to have some issues
• modem-manager-autosetup: Proceed with configuration even for unknown service providers

:boom: Breaking Changes
• Drop experimental mwifiex-nxp driver (not used by us anywhere)

As always, if you encounter any new issues, please let us know.

10 Likes

Three months after 7.0 release? And where is TOS 8?

In HBD :wink:

3 Likes

And when will they be in HBL?

After we release 7.1

When we are sure that the automatic upgrade and migration to nftables will work smoothly and wouldn’t break peoples firewall.

3 Likes

Thanks. And when will the first test version of TOS 7.1 be available?

Is reboot required for this update?

My Turris 1.x showing no update available. Current version 7.0.0

Hmm, something is not going as expected?
The Reforis update says no, the Luci individual software packages updater shows a lot of updates/upgrades ready for upgrade.

Is the not-all-users-at-once update policy still on maybe?

edit : yes

WARN:There is a newer version available, but update is scheduled after another 218.6 hours. If you want the latest and greatest all the time, switch to one of the development branches.
INFO:Target Turris OS: 7.0.0

Staged rollouts. Maybe turris team could let us override this somehow, maybe even from the Foris UI…

For these less-risky updates (no kernel update) we could prioritize speed, since there’s little risk of breaking end user’s routers…

And a bigger risk in staying out-of-date for longer - since this is mostly a security update.

Well, not sure how critical this openssh fix is, but me think it might be useful to mention the staged part in the announcement.
Not all ( mostly me) might be aware of this with these small fixes.

Ps, we still have this section:

This is due to the staging updates being turned on.

Reboot after the update is strongly recommended.

We do not want to allow users to override this option because it would defeat its purpose and result in the same functionality as delayed updates, which users can set up themselves. The purpose of the staging updates is to give us time to deal with problems which might arise in waves. Therefore, allowing overrides would enable users to skip these stages and present all problems, which might arise, to us at one point.

Nonetheless, as this is a security update, the staging should have been set to short periods or turned off completely. We apologize for the inconvenience and will try to fix this as soon as possible.

5 Likes

TO 2016, HBS branch, 2 GB, 2x WiFi, HaaS, RIPE Atlas, Sentinel, lxc, SSD (logs etc), simple config, all seems OK.

The staged updates for this particular update have been disabled today. All devices should be able to update itself from now on.
We apologize for the inconvenience.

1 Like

Ah, this is why my turros poked me today for a reboot :wink:
Seems to work as smoothly as expected. Thanks!

1 Like

I got the update as well. All sems fine so far. Thanks for the release.

1 Like