The following describe the problems resolved in this maintenance release of the NCP Secure Entry Mac Client.
Problem description: Firewall not working after system caches have been deleted
After the Mac OS X system caches have been deleted (e.g. by maintenance tools), those system caches are automatically regenerated during the next new start. Generating the system caches takes some time, lengthening the start phase of the processor considerably. Expiry of a particular timer during this lengthened start phase could make the VPN Client, including the firewall, inoperable.
Problem resolution: The timer has been set to a default value that ensures this problem no longer occurs.
Problem description: VPN Tunnel not working when connection from Mac OS X was over PPPoE or GPRS / UMTS
When an Internet connection from Mac OS X was established over PPPoE or GPRS /UMTS, the firewall could not filter the data transferred over this connection and so a working VPN Tunnel was not created.
Problem resolution: A driver for the PPP adapter has been implemented, which integrates some GPRS / UMTS adapters. This driver implementation has resolved this problem.
Problem description: Multiple starts of the Client overwrote the stored profile settings
Problem resolution: The Secure Entry Mac Client can now only be started once per processor. This ensures that, on a started Client, if a second user performs a "fast user switching" and a restart of the Client, the profile settings of the Client are not overwritten.
Any pre-existing VPN connection of the Client is not affected by a change of user; the connection remains in existence.
Problem description: Incorrect handling of IP addresses during configuration import
During configuration import, the IP addresses from the profile settings configuration area "IPsec Address Assignment" and "Split Tunneling" were handled incorrectly.
Problem resolution: IP addresses are allocated correctly in this maintenance release.
Problem description: Timeouts ineffective with pre-connected NAT devices
If the Secure Entry Mac Client is located behind a NAT device (router that performs Network Address Translation), it independently sends IKE-Keep-Alive-Packets at a pre-defined polling interval. In the previous version, this data stream inhibited the action of a timeout, configured in the "Connection Controls" profile settings.
Problem resolution: This problem has been resolved.
Problem description: Client Error Messages
Problem resolution: Client error messages in the monitor and log window have been re-worked.
Problem description: Incomplete messages in firewall-log
After removing a network adapter or terminating a PPP based connection, the firewall-log was no longer up-dated. However, the firewall functionality was not affected by this fault.
Problem resolution: This problem has been resolved; the firewall-log is now correctly up-dated under the conditions described.
Problem description: PAP/CHAP error when using XAUTH
If a VPN connection has been initialized directly after the start of the VPN client, without changing a preset profile, the connection could not be established because of a PAP/CHAP error during the XAUTH negotiation.
Problem resolution: This error has been resolved. A proper VPN connection, after the PIN request, can be established.
Features of the previous release 1.00 build 78:
Operating Systems
Mac OS X 10.5 Leopard (Intel) and Mac OS X 10.6 Snow Leopard
Security Features
The NCP Secure Entry Mac Client supports the Internet Society’s RFC 4301 – Security Architecture for the Internet Protocol (IPsec) and all the associated RFCs.
Personal Firewall
Virtual Private Networking
Encryption and Encryption Algorithms
Symmetrical: AES 128,192,256 bits; Blowfish 128,448 bits; Triple-DES 112,168 bits;
Asymmetrical: RSA bis 2048 bits, RSA to 2048 bits, dynamic processes for key exchange
Perfect Forward Secrecy
FIPS Inside
The IPsec Client incorporates cryptographic algorithms conformant to the FIPS standard. The embedded cryptographic module incorporating these algorithms has been validated as conformant to FIPS 140-2 (certificate #1051). FIPS conformance will always be maintained when any of the following algorithms are used for establishment and encryption of the IPsec connection:
Authentication
Hash / Message Authentication Algorithms
Public Key Infrastructure (PKI) - Strong Authentication
Networking Features
Any type of network, iPhone tethering via USB or Bluetooth
Network Protocol
IP
VPN Path Finder
NCP VPN Path Finder Technology, Fallback to HTTPS (port 443) from IPsec if neither port 500 nor UDP encapsulation are available (prerequisite: NCP Secure Enterprise Server V 8.0 and later)
IP Address Allocation
DHCP (Dynamic Host Control Protocol);
DNS: Anwahl des zentralen Gateways mit wechselnder öffentlicher IP-Adresse durch Abfrage der IP-Adresse über einen DNS-Server
Line Management
Dead Peer Detection with configurable time interval
Data Compression
IPCOMP (LZS), deflate
Additional Features
UDP-Encapsulation; Importfunktion der Dateiformate: *.ini, *.pcf, *.wgx, *.wge und *.spd.
Internet Society RFCs and Drafts
Client Monitor (Intuitive Graphical User Interface)
*) If you wish to download NCP's FND server as an add-on, please click here: http://www.ncp-e.com/en/downloads/software.html
More information on NCP Secure Entry Client is available on the Internet at: http://www.ncp-e.com/de/http://www.ncp-e.com/en/solutions/vpn-products/universal-ipsec-client.html
Eine kostenlose 30-Tage Vollversion können Sie hier herunterladen: http://www.ncp-e.com/en/downloads/software.html