Access Server release notes for 2.1.12 (changes made since 2.1.9)

* Problems with gaps in sequentially ordered lists of keys in the configuration database are now automatically repaired when using sacli start on the command line.* TLS level 1.2 for the OpenVPN protocol is labeled the default for new installations. Upgrades of existing installations remain at the previously set level.* TLS level 1.1 for the web services is labeled the default for new installations. Upgrades of existing installations remain at the previously set level.* SSLv2 and SSLv3 support has been deprecated and will be removed completely in a future release.* SSL settings page is now renamed to TLS settings page, since TLS is now the prevalent technology and SSL is phasing out.* Alias interfaces like eth0:1 and such could not be selected for source NAT outgoing VPN client traffic. This bug has now been fixed.* An option has been added to completely disable TLS auth. This should only ever be used for compatibility with clients that offer no way to implement TLS auth at all.

Access Server release notes for 2.1.6 (changes made since 2.1.4)

*OpenVPN Connect Client for Mac OS X updated to version 2.1.3.120 to address the "error no. 8" bug that occurred on some systems that have an IPv6 DNS server assigned as primary DNS server.

*OpenVPN Connect Client for Windows updated to version 2.1.3.111 to address the problem where an autologin type profile would endlessly loop in reconnection state when the autologin profile encounters an authorization problem (no longer valid, revoked, and such).

Access Server release notes for 2.1.1 (changes made since 2.1.0)

* The previous "Default Domain Suffix" field is now used to set the "dhcp-option ADAPTER_DOMAIN_SUFFIX ..." OpenVPN setting.

* Connect client: Fixed an installation issue where the service component would not start after installation. Affected only a few specific situations, and is now resolved.

* NOTE: DNS behavior is slightly altered since version 2.1.0 of the Access Server. If you encounter problems please review your settings in the Admin UI under VPN Settings, specifically the section for DNS settings.

Access Server release notes for 2.1.0 (changes made since 2.0.26)

* Windows client routing : use the "route-metric" directive (which may be pushed) to set the gwmetric on TAP interface

* client routing : add pushed routes even when redirect-gateway is also pushed.

Access Server release notes for 2.0.7 (changes made since 2.0.6)

Access Server release notes for 2.0.6 (changes made since 2.0.5)

* Updated OpenSSL to 1.0.1g to fix CVE-2014-0160 (aka Heartbleed vulnerability). This is a critical vulnerability, and all Access Server users are advised to upgrade immediately.

(Note: If you would like to patch the OpenSSL libraries for older versions of Access Server please download the libs for your distro and copy them into /usr/local/openvpn_as/lib from here: http://swupdate.openvpn.org/hb/)

Access Server release notes for 2.0.3 (changes made since 2.0.2)

* Fixed issue where an invalid port (or port range) specified for DMZ in the User Permissions page would be silently ignored, with no error message.

* Added a potential improvement on the iptables rule generation for DNS packets.

* Extended the "Allow Access To these Networks" field in User/Group Permission pages to allow the full route specification syntax supported by the backend, including subnets, services, port ranges, and NAT vs. Routing flag