Re: Win CIPE|
"Damion K. Wilson" <dkw,AT,rcm,DOT,bm>|
Mon, 15 Jan 2001 17:36:54 +0100|
I am a Unix man, too (11 years admin + programming) so I understand where
you're coming from.
CIPE-Win32 is implemented in two parts: a tap device driver which
implements a network interface on one side and a character stream device on
the other, and a user mode daemon which implements the CIPE protocol. The
TAP device is implemented in the same manner as the TAP device in the
TUN/TAP project. It would seem that you could use the TAP device unmodified
and build an SSL tunnel in a usermode.
I am interested in your motive. Is CIPE somehow inadequate or do you have
to integrate with an existing infrastructure ?
*********** REPLY SEPARATOR ***********
On 1/15/01 at 7:43 AM Peter Stamfest wrote:
>Sorry to contact you privatly and not via the list, but I would like to
>ask some questions regarding CIPE. I have discussed a similar topic on the
>openSSL mailing list, but I have been beaten for it....
>What I have in mind is to develop a free VPN client for Windows - now you
>will say that this is what you have done, but I would like to couple it
>with openssl and x509 certificates.
>Before you start telling me about SSL being TCP only, I would like to add
>that I would like to see encapsulation over UDP packets.
>I am a UNIX man, so I am looking for Win32 programmers to talk to about
>Do you think that Win CIPE could be a basis for such a development? I
>haven't gone into details with CIPE, but for my OpenSSL project I am
>thinking about a kernel side driver and a user-space Windows service
>to handle the cryptographic stuff.
>Do you think that this is compatible wioth CIPE?
>Any input is welcome, and again, sorry for contacting you privatly.
>Peter Stamfest UNIX, Networking & Computing Consultant
>Tel: +43/699/20711205 Software Development - Internetservices
>E-Mail: ps,AT,psncc,DOT,at WWW: http://www.psncc.at/