To confirm, yes - the release for v18 MR3 has been unfortunately delayed and will not be released this week. Please stay tuned next week, as we'll continue to follow up with the development teams to share updates for the Community.
I can only recommend you one thing ... Don't. v18 is mostly about two things. Decoupled NAT, and TLS/SSL Inspection rules. The later does not work. Source of continous problems and slowing down everything to a crawl. You can live with coupled NAT. So. Wait at least another year. Seriously. Other wise you'll be part of Sophos Q&A team liking it or not. And your customers will want to hang you.
Big_Buckis right about the TLS/SSL Inspection Rules; it just doesn't work. You will pull your hair out trying to troubleshoot why sites randomly either fail to load or load extremely slowly. Loved getting the panic call from our HR people who couldn't process payroll because the site wouldn't load halfway through. The answer you'll get from Sophos is "Make an exception" but when you observe that somewhere around 30% of sites have problems, that's not a practical or realistic or serious answer.
Part of the reason I've been so interested in MR3 is the hope that there are major improvements to the TLS/SSL engine, but I'm not holding my breath anymore.
Make exception rules was what I was told too. If you look at Sophos own built-in exception rules (for Microsoft updates for example), you'll notice that many of them disable ssl inspection very widely to a point it is not usefull anymore.
I'm afraid they would have to fire everyone who had anything to do with a firewall rules, NAT rules and TLS / SSL rules too. So is it about half of all developers? I think they would definitely deserve it, but I'm afraid it didn't happen ....
That is true, but it has been cut across all departments. It was not aimed at incompetent developers. Unfortunately, it also affected workers who were very capable and were definitely a benefit to Sophos. When the forest is felled, splinters fly - we say here.
