I think you are referring to ms's proprietary PPTP, point to point tunneling
protocol, where they developed their own badly flawed key generation
algorithm, hash functions, authentication protocol, then topped it off with
an incorrect implementation of an encryption algorithm, which destroyed its
security features. The result: °º©Æø¿£¡`~ÐðÞþ
Smitty
>
> In a book I have on VPN (Building Linux VPNs) the authors says if you for
> some resaon have to support ms vpn "..we offer our deepest sympathies."
> Hehe.
>
> There's no coincident OpenSSH is made by the OpenBSD people. Solid product!
>
> On Monday 17 June 2002 12:17, Ian C. Blenke wrote:
> > On Mon, 2002-06-17 at 10:05, JVergara@equinox.com wrote:
> > > Hi,
> > >
> > > Does somebody have a clue of how to connect a Windows client (98-
> > > W2K) from home to a Samba shared volume in
> > > a Linux server at work - via VPN?
> >
> > Yes. Via a full VPN, or some form of a TCP tunnel of port 139 and/or
> > 445.
> >
> > > Let's state that the Samba Server is connected thru the Internet with
> > > DSL connection even though its TCP port is not exposed to the public
> > > network and the Windows client has a Internet dialup connection.
> > > what software do I need in both sides ?
> >
> > Well, if you have sshd running on "workgateway" (which can be
> > "sambaserver" machine itself or a firewall in front of it), and you
> > don't have Microsoft filesharing enabled on your Win98/Win2k client
> > machine, it's rather easy:
> >
> > ssh -L 139:sambaserver:139 workgateway
>
> snip
>
> > SSH is my friend.
> >
> > - Ian C. Blenke <icblenke@nks.net> <ian@blenke.com>
> > http://ian.blenke.com
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 12:49:11 EDT