NCP Secure Entry Client for IPSec VPNs
NCP Secure Entry Client with regard to communication with any IPSec gateway (compatibility list in http://www.ncp.de). It supports almost all transmission networks like ISDN, the analog network, xDSL, Internet, GSM, GPRS, IMTS, LAN, WLAN, and this runs under all Home windows operating systems. A permanently incorporated Personal Firewall shields the particular PC against attacks inside all communication environments. Almost all security mechanisms are currently active when the program starts and they stay active until the Access Client is deactivated. IP-NAT, Stateful Packet Inspection, described filter rules, Friendly Internet, and hotspot detection (automatic detection from the current system environment and activation associated with the corresponding filter rules). Authentication relative to the particular destination gateway can end up being executed via OTP tokens or certificates (soft certificates, smart cards, USB tokens) inside a PKI, at your own discretion. All data are usually encrypted for transmission. Assistance for: Triple DES 128, 192-bit, Blowfish 128-bit, AES 128, 192, 256-bit, plus RSA 1024, 2048- little bit. The Entry Client may also be implemented inside it environments without permanent IP addresses. DynDNS (Dynamic DNS) is used to dial-in towards the central VPN entrance with changing public IP addresses which are queried via a public DynDNS server (prerequisite: the location gateway must support DynDNS). As an alternative in order to the Microsoft RAS autodialer the Entry Client offers its own dialer that is operating-system independent. It gives these advantages: telephone cost savings, handover and marketing of central VPN sources through intelligent Short Keep Mode, remote administration, plus protection from outside dialers.
|
Requirements :
64 MB RAM, 10 MB HD
|
|
NCP Secure Entry Linux Client
By 3 Users
Downloads
: 5
