After reading this article, I was wondering what is or can be done to protect devices running UT from this vulnerability. As far as my knowledge goes, UT uses an android kernel, which uses device specific and mainly closed source hardware drivers. The white paper says that the vulnerability can be mitigated through software or firmware updates, but older devices don't get firmware updates anymore.
My question is whether UT users will stay vulnerable to Kr00K as long as there is no firmware update available or can it be solved through software and is it just a matter of capacity and priority?

Basically the same question applies to Spectre, Meltdown and other bugs where the source is in the hardware.

I have been using this method, Wifi hotspot and Nexus4,
to enable a hotspot on my Nexus 4 with OTA-15 an -16.
However, after upgrading to OTA-17, other devices can connect to my hotspot, but there is no data transfer.
Connected android devices report "connected, no internet" Any thoughts how to fix it?

After reading this article, I was wondering what is or can be done to protect devices running UT from this vulnerability. As far as my knowledge goes, UT uses an android kernel, which uses device specific and mainly closed source hardware drivers. The white paper says that the vulnerability can be mitigated through software or firmware updates, but older devices don't get firmware updates anymore.
My question is whether UT users will stay vulnerable to Kr00K as long as there is no firmware update available or can it be solved through software and is it just a matter of capacity and priority?

Basically the same question applies to Spectre, Meltdown and other bugs where the source is in the hardware.

Is there an alternative available for the Microsoft Authenticator app in Ubuntu Touch Stable?
The Authenticator NG app from the Openstore does not recognize the QR code that is supposed to be used to register the MS Authenticator. If trying to manually set up the account, I have to enter a nine digit activation and a phonefactor URL. I can only control the client side of the connection, my guess is that the server side uses Azure AD.

@tera Thanks, that solved the issue

If I open an SSH session from the terminal app to my Ubuntu server, this process appears to be paused after switching from other apps back to the terminal app. I'm able to resume the SSH session with command fg %1, but after resuming the terminal acts differently. That means commands are echoed after pressing enter, but before executing them and arrow keys result in control characters (^[[A for arrow up, ^[[C for arrow right etc) being printed to the terminal.
This behaviour seems to be more an SSH issue, than an UT issue. Because the same happens if i send SIGSTOP to SSH sessions from laptop to server or laptop to UT.
The display behaviour is similar to this and this issue, but I checked in my case the shell is always bash and $TERM doesn't change before and after the pausing of SSH.
Is it possible to either prevent the SSH session being paused during app switching or to fix the terminal behaviour after resuming the paused session?

It's possible to mount SMB/CIFS shares from the command line.
First you need to install the cifs-utils package, which requires remounting root to make it writeable. Than the network share can be mounted with:

mount -t cifs -o sec=ntlmssp,username=user,password=pass,iocharset=utf8,vers=1.0,rw //servershare ~/'directory to mount to'

I recently reported a bug for a Nexus 4 running OS build number 2018-W48. The same behavior is also present on a Nexus 5 running OS build OTA-5. Should I add this information to the existing report or is it better to file a new report?