Turris OS 3.7.2 out with security fixes

Community office
1

Dear Turris users,
after few days of heavy testing, we just deployed Turris OS 3.7.2 for everyone. It is mainly about fixing security issues.

Changes are:
• kernel: security update to the newer version
• php: security update to the newer version
• bind: security update to the newer version
• pcre: security update to the newer version
• gnutls: update to the newer version fixing various issues
• updater: fixing various small errors
• unbound: update to the newer version fixing various issues (Turris 1.x only)

The whole Turris team wishes you smooth update process and we are looking forward to reading your feedback!

3.8 should be out in few weeks with interesting new features.

7 Likes
2

Everything went well for me! :sunglasses:

1 Like
3

I have an error message in the yellow box:
“Chyba z 20. 07. 2017 19:19:23
Updater selhal: Chybí CRL, pravděpodobně je problém v připojení k internetu.”

The internet connection is OK.
(Turris 1.1)

1 Like
4

I had to reboot twice, the first time I had constant reconnections to the 5GHz WiFi.

I also got two warnings:

WARN:Script revision-specific not found, but ignoring its absence as requested
WARN:Script serial-specific not found, but ignoring its absence as requested
5

updated smoothly for me. notifications about user modified /etc/config/updater and /etc/updater/auto.lua but that’s not a surprise.

6

This one is OK. And perfectly normal.Yet it could get better :slight_smile:

1 Like
7

The same issue in my case with Turris 1.0

1 Like
8

The same in my case (on Turris 1.0)

So … I think this is not bug, but feature! :slight_smile:

1 Like
9

Turris 1.0 OK (clear configuration)
Omnia 2GB - OK

1 Like
10

Turris 1.0 without any specialities OK after restart :wink:

1 Like
11

I just received the same error message via email notification from my Turris 1.1.

12

Is it just me, or has ntfs-3g been removed?
I’m using 2 ntfs drives, but they won’t mount regardless of what I do. When trying to run the mount scripts directly via SSH, all I get is “-ash: nas: not found” despite it being there, so I’m guessing it’s missing dependencies

EDIT: I tried force reinstalling ntfs-3g and ntfs-3g-utils, no change.

EDIT2: seems like a reset init.d path, running ./nas start did the trick /facepalm

13

I received same error message from Turris 1.0 too :frowning:

14

After the upgrade, Turris Omnia had a brain-fart… Turn it off then back on… Now it is working…

I do see errors in the System Log after the restart:

2017-07-24T19:51:58+08:00 warning kernel[]: [ 14.783329] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/pre-cal-pci-0000:02:00.0.bin failed with error -2
2017-07-24T19:51:58+08:00 err kernel[]: [ 14.803814] firmware ath10k!pre-cal-pci-0000:02:00.0.bin: firmware_loading_store: map pages failed
2017-07-24T19:51:58+08:00 warning kernel[]: [ 14.812955] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/cal-pci-0000:02:00.0.bin failed with error -2
2017-07-24T19:51:58+08:00 err kernel[]: [ 14.832901] firmware ath10k!cal-pci-0000:02:00.0.bin: firmware_loading_store: map pages failed
2017-07-24T19:51:58+08:00 warning kernel[]: [ 14.919158] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/QCA988X/hw2.0/board-2.bin failed with error -2
2017-07-24T19:51:58+08:00 err kernel[]: [ 14.939291] firmware ath10k!QCA988X!hw2.0!board-2.bin: firmware_loading_store: map pages failed

What are these errors???

15

It could happen before the update. This message basically says that the connection to the update server failed in the past. Don’t worry if you don’t see it very often and I promise that we will make it more pretty in future updates.

16

I am sorry for the two reboots, I don’t know why that happens.

Warnings just say that there is no special update for your HW revision or serial number. So no problem.

17

Don’t worry, @Petr_Weinfurt and @davitjan1, there shouldn’t be any problem.

18

How often? Every time I restart Turris :slight_smile:

19

There is a way to resolve it?

20

If yes, it could be that your Turris is trying to reach update server before it has IP leased and proper connection.

Not at the moment.