Remarks:
Middleware will be restarted
Active IP and VPN connections will be restarted
Existing configuration will not be changed
News:
Added new Antispam Engine for Email scanning
Fixed several problems with WebAdmin and SSL VPN ports
Fixed lots of small issues and browser problems
Bugfixes:
Fix [5468]: Definition dialog boxes with fixed width only
Fix [5711]: IPSec tunnels may not come up after DPD event
Fix [5747]: Intrusion Protection counter in dashboard incorrect
Fix [5778]: User objects not allowed as source/destination in DNAT/SNAT rules
Fix [5786]: SHA-2 with 512 bit not compatible with NCP/ASC IPSec client
Fix [5789]: User certificate will not be deleted at all
Fix [6031]: HTTP traffic in cluster may not be distributed to worker
Fix [6265]: Portscan detection and logging consumes too much CPU resources
Fix [6320]: POP3 spam email not tagged correctly
Fix [6333]: Drag-and-drop fails with Internet Explorer
Fix [6375]: Contentfilter whitelist does not use regular expressions
Fix [6421]: HTTP Proxy does not log complete URL
Fix [6510]: Up and down arrows don't work correctly in HTTP Profiles
Fix [6571]: L2TP daemon will not be restarted automatically
Fix [6607]: Daily Spam Report may not be sent out correctly
Fix [6618]: HTTP Proxy closes sessions after response
Fix [6639]: Timezone glitch in WebSecurity Reporting
Fix [6692]: Interface used in Dyndns settings can not be removed
Fix [6703]: Automatic import of SMIME certificates not working correctly
Fix [6713]: Changes to backend query order do not take effect
Fix [6715]: Remote Syslog logs without facility and priority
Fix [6716]: L2TP over IPsec offers wrong certificate
Fix [6732]: Can not change PPPoE Daily Reconnect Time to 'never'
Fix [6740]: Authentication of new users may fail
Fix [6772]: SMTP Mail processing may stop completely
we have found out that in some cases the authentication daemon gets not restarted properly. So far this seems to only happen on slower machines.
Can you give us information what kind of hardware has been used (CPU, RAM, RAM/SWAP usage) in the system where the login was no longer possible after the reboot?
as an alternative to rebooting you can also log into the box via SSH and do /etc/init.d/aua start
This will start the authentication daemon and the login is than possible again.