Preliminary Information - Subject to change
Make Secure Connections (SSL) with Any TCP/IP
SecureWrapper can be used with any TCP connection. TCP Connections
include, TELNET, NSVT, FTP, SMTP, and other application specific
protocols. This includes, but is not limited to, ODBC, OLEDB, WS92,
VisualLink, other terminal emulators, and other 3rd party applications.
SecureWrapper is a network tool used to provide a means to add
security to a single application or group of applications communicating
across a network.
SecureWrapper provides a smaller set of features than a VPN with
much less overhead. You can tailor the applications protected without
forcing all network connections to share the same VPN resource.
Use SecureWrapper where there is a need for secure communications
and the source code needed to change either the client and server
SecureWrapper uses the same codebase as secure NSVT communications
method of Secure92.
Comparison to OpenSSL Wrapper (stunnel)
The bits and bytes of the communications protocols are the same
(based upon standards).
SecureWrapper differs in being built specifically for Windows
(rather than for Unix with Windows an additional platform).
We offer simplified, GUI based, configuration. There are no confusing
or cryptic command line options for the end-user.
SecureWrapper can be configured to prevent end users from making
any changes that could reduce the level of protection. When configured
as a server, there is no place for a end-user to change the pre-set
configuration. As an application, SecureWrapper prompts the end-user
for authentication credentials (username and password) then sits
in the background until they log out.
SecureWrapper is supported where the OpenSSL Wrapper (stunnel)
tools are open source.
SecureWrapper may be installed as either a Windows service or
application. As an application, the end user would provide authentication
(username and password) after logging on to the PC. The service
would be configured to store authentication information and allow
any user of the PC to connect.
In the sample below, SecureWrapper would be installed on the
PC. The host system (HP3000 in this case) would not have a NAT address
mapping rendering it virtually inaccessible from outside the firewall.
Using this configuration, client applications could access an HP3000
server applications using an SSL connections without modifications
to either the client application or the server application. Additionally,
local users would continue to have direct access to the HP3000 applications.
With SecureWrapper set to listen on Local Port 1570, the SSH
Host set to 184.108.40.206, and the host address set to 192.168.0.188;
any application running locally on the PC would be able to open
a connection to 127.0.0.1:1570 that SecureWrapper would forward
to the HP3000.
SecureWrapper2 - Application
SecureWrapper - Service
CREDIT INFORMATION: This product includes cryptographic software written by Eric A. Young (firstname.lastname@example.org). This product includes software written by Tim J. Hudson (email@example.com).