This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Sophos UTM update 9.411-3 released

Up2Date 9.411003 package description:

Remarks:
System will be rebooted
Configuration will be upgraded

News:
Maintenance Release

Bugfixes:
Fix [NUTM-6804]: [AWS] Update breaks HVM standalone installations
Fix [NUTM-6747]: [Email] SAVI scanner coredumps permanently in MailProxy after update to 9.410
Fix [NUTM-6802]: [Web] New coredumps from httpproxy after update to v9.410

RPM packages contained:
rubygem-sophos-iaas-1.0.0-0.251808053.g8ec3939.i686.rpm
ep-cssd-9.40-28.g1a032c7.rb1.i686.rpm
ep-ha-aws-9.40-376.g8ec3939.noarch.rpm
ep-cloud-ec2-9.40-47.g1d126b2.i686.rpm
ep-httpproxy-9.40-393.g39ad256.rb5.i686.rpm
ep-release-9.411-3.noarch.rpm



This thread was automatically locked due to age.
Parents
  • After the update to 9.411-3 we noticed that usergroup networks aren't resolved correctly anymore. specifically, if a User is a member in multiple Groups, only about the first 3 groups get the users IP registered if the user connects through SSL VPN, which breaks most of our firewall rules regarding VPN Access.

Reply
  • After the update to 9.411-3 we noticed that usergroup networks aren't resolved correctly anymore. specifically, if a User is a member in multiple Groups, only about the first 3 groups get the users IP registered if the user connects through SSL VPN, which breaks most of our firewall rules regarding VPN Access.

Children
No Data