We'd love to hear about it! Click here to go to the product suggestion community
9.506 is released.
Maybe we could use this thread for reporting successful updated system and maybe not so many bugs. Who wants to be first to update? :-)
In reply to Alexander Busch:
WAF is broken for me.
It affects Windows 7 clients using Outlook 2010 connecting to Exchange 2010.
Other combinations like Windows 10, or Outlook 2013 work fine.
TLS 1 is required somewhere in this chain.
9.505-4 added a TLS Verion dropdown that allowed you to pick you Min. TLS level.
9.506-2 removed the option.
I have an open support ticket, do not have a work around yet.
I was sent this as a workaround:
It doesn't seem to apply since the lines Sophos references to change no longer exist in the file.
Hope this helps,
In reply to RonVer Mulm:
Latest Update from Sophos Support.
If I understood correctly.
TLS 1 support has been removed.
Ron, what does the following give you?
cc get reverse_proxy min_tls
Cheers - Bob
In reply to BAlfson:
After you do: cc set reverse_proxy min_tls 1
Check the result with: grep SSLProtocol /var/chroot-reverseproxy/usr/apache/conf/reverseproxy.conf
Now is WAF still "broken" for that one situation?
Note that this probably is not supported and that you should upgrade your software to eliminate its dependence on TLSv1. After upgrading, use the trick above to set the value back to 1.1.
TLS 1.0 and TLS 1.1 are no longer considered safe encryption technologies, so this should not be a surprise. However, the change should have been in the release notes. I have complained about this before.
I infer that your problem is on the client side, since you said the problem only affects Windows 7. Windows 7 shipped with TLS 1.0 installed but not enabled, for reasons that defy explanation. You can turn it on by GPO or manually within Internet Options.
Reconfiguring your clients is a better idea than decreasing UTM security, but you can probably re-enable TLS 1.0 and TLS 1.1 by editing this file:
Change this line:
SSLProtocol +TLSv1.2toSSLProtocol +TLSv1.0 +TLSv1.1 +TLSv1.2
Note1: Never enable TLS1.0 without also enabling TLS1.1 The session compatibility search functions do not like gaps in the search sequence.
Note 2: I also recollect that Exchange 2010 had a problem with SMTP supporting nothing higher than TLS 1.0, but I believe it was corrected in one of the Exchange cumulative updates, because my configuration is connecting with TLS 1.2.
In reply to DouglasFoster:
Doug, if you look at my last post above, you'll see that this line is no longer in httpd.conf, but in reverseproxy.conf. Unfortunately, that gets rewritten too often. Also, if min_tls is 1.1 as Ron says, that line will look like SSLProtocol -all +TLSv1 +TLSv1.1 +TLSv1.2 after the cc set I mentioned.
That said, I admit that I didn't read his post closely enough to had your insight about the client. I bet that's the best solution.
I think I found the minimum TLS version setting, its been moved to the Web Application Firewall-Advanced tab. I'm still seeing the option for TLS v1 or higher. When I run cc get reverse_proxy min_tls it returns 1.
Web proxy does not use any filter in Blocked File Extensions, MIME filters or. Warned MIME Types
You are my HERO today!
My clients are connecting again.
Now maybe after a couple of hours outage, I can get them to get their software upgraded...
The main issue is I told them they had until April 2018 to fix this as that is the PCI compliance deadline for TLS 1.
I didn't comprehend this line in the change log:
Fix [NUTM-8806]: [WAF] Issue with TLS settings for virtual webserver
Meant removal of TLS 1...
In reply to SteveU:
Thanks a bunch for finding that!
Not as cool as per server, but I can live with it.
TLS 1 is still there you just need to know what screen to access.
Advanced vs Virtual Webserver/Edit Screen.
I guess I was writing my reply as you were writing yours. Thanks for the updated information.
Someone Please clarify: WAF encryption options are supposed to be configurable from the GUI, but I thought that was only for AWS environments. Is it actually supported for all configurations in 9.506?
After updating my ESX setup, both nodes of the HA cluster (running on different ESX hosts) come up with the same MAC adresses. The "cc ha set virtual_mac 0" works, but only acts on the HA interface, which does use the physical interface MAC.
So it broke my cluster, and my redundancy. Not amused. :-(
In reply to HarroVerton:
SMTP Proxy - authentication. Can't select AD server even though I have 4 of these listed in the UTM