PLEASE READ Advisory: Kernel memory issue affecting multiple OS (aka F**CKWIT, KAISER, KPTI, Meltdown & Spectre) for the latest updates.
We'd love to hear about it! Click here to go to the product suggestion community
UTM 9.502 has been Soft-Released today and can be found on the FTP server as usual:
IMPORTANT: The re-join workaround is required after upgrading to 9.502. See: https://community.sophos.com/kb/en-us/126819
[Edit]: Moved Workaround into a KBA.
I'd been told that this release would fix issue NUTM-7960 but I can't see it listed?
In reply to steveatkinson:
That's correct and it's in. It somehow slipped through the changelog query. I add it manually to the list above.
and again no update / information about waf and exchange 2016 ;(
NUTM-8161 [Access & Identity] OpenVPN vulnerabilities (client part)
Does this mean that we have to redeploy the SSL-VPN Clients?
Look again and you will see it. Let me know if you upgrade to this new version and you finally fix the authentication problem.
In reply to Carlos Paradela:
It might be there now but it wasn't earlier, and it also wasn't in the release txt file!
I'm upgrading overnight so will see what the morning brings...
Well, let's pray now and hope it works again good. I'm still getting problems, but I'm using a lower version (9.414-2, also affected) and at least works better than 9.501-5. I wish you good luck and if you can tell me tomorrow I will appreciate it.
IMPORTANT: The re-join workaround is required after upgrading to 9.502.
The re-join can be done by following these steps:
Good morning Carlos,
I did the update last night and now AD SSO appears to be working normally, no other issues that I've noticed have been caused by this update.
Might not be the same for you but hopefully will be!
We also patched to 9.502-4 and it do not work.
AD SSO Standard Auth. Domain rejoined and Client restarted - No connection to https websites.
Which was your previous Version? 9.501?
In reply to MarcelLiechti:
Yes, that is correct. and the bug I had was NUTM-7960
In reply to talex:
I cant join the domain now after doing this. "Failed to Join Domain" every time.
In reply to James Roughley:
I had that problem previously, but disappeared with a reboot, might be worth trying if you haven't already
1st thing I did Steve.