Index of /ressources/outils/ssltunnel/download/windows

[ICO]NameLast modifiedSizeDescription

[PARENTDIR]Parent Directory  -  
[   ]ssltunnel-windows-1.16.0.3.zip2014-01-23 16:54 961K 
[   ]ssltunnel-windows-src-1.16.0.3.tar.gz2014-01-23 16:54 106K 
[IMG]startconn.png2014-01-23 16:54 9.9K 
[IMG]config.png2014-01-23 16:54 9.0K 
[IMG]disconnect.png2014-01-23 16:54 8.3K 
[TXT]README.txt2014-01-23 16:54 1.9K 
[   ]README2014-01-23 16:54 1.9K 
[TXT]ssltunnel-windows-src-1.16.0.3.tar.gz.asc2014-01-23 16:54 189  
[TXT]ssltunnel-windows-1.16.0.3.zip.asc2014-01-23 16:54 189  

# $Id: README,v 1.3 2004/09/19 13:11:48 thivillon Exp $

This is SSLTunnel Windows client.

SSLTunnel is a VPN tool to build PPP tunnel over SSL/TLS connections.
It can be used in any environment, including firewalled connections
allowing only HTTPS over authentified proxy.
See:
 - http://sf.net/projects/ssltunnel
 - http://www.hsc.fr/ressources/outils/ssltunnel

Windows client is known to work on Windows 2000, XP (SP1 and SP2) and
Windows Server 2003. 

To setup your tunnel, you need:
- a SSLTunnel server installed on a Unix host with a port (preferably
  443) accessible from the Internet.
- X509 Certificate, Key and CA Certificate. You can read 
  https://sourceforge.net/docman/display_doc.php?docid=21843&group_id=89578
  to create them.

SSLTunnel client for Windows includes:
- a device driver (PPPoP), which implements a Miniport Driver. This driver
  emulates an ISDN line: it takes PPP packets from NDIS stack, send 
  them into \device\pppop, and symmetricaly read \device\pppop and
  send ppp packets to NDIS.
- a command line userland application, which listen to \device\pppop,
  wait for a TAPI request relayed by PPPoP , "dial" (connect to) tunnel
  server, authenticate with X509 certificates then relay packets between
  network and kernel.
- a Windows Service, which can be used to replace command line interface and can
  create multiples tunnels. 
- a GUI client, which can be used to create config files for Service or
  CLI, and can launch tunnels in a nice (?) traditionnal Windows interface.

All of these three tools use the same tunnel.dll DLL.

You should start tunnel with one of these tools, which will wait for
connection requests, then connect to server using Windows RAS. GUI tool
can start RAS automatically, i suggest you start manually during testing.

Installation of programs and driver is at this time a manual task, and
is described in install-english.pdf file in binary archive.