Re: XP client & Server authentication
From: Steven L Umbach (n9rou_at_nospam-comcast.net)
Date: 05/27/05
- Next message: Robin: "Re: XP client & Server authentication"
- Previous message: Robin: "Re: XP client & Server authentication"
- In reply to: Robin: "Re: XP client & Server authentication"
- Next in thread: Robin: "Re: XP client & Server authentication"
- Reply: Robin: "Re: XP client & Server authentication"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Thu, 26 May 2005 22:32:05 -0500
You made a good choice as L2tp/ipsec is a very secure way to tunnel through
any public network and features encryption, computer and user
authentication, integrity, and anti reply protection once you have
successfully connected to your VPN server. If the concern is that you will
connect to a bogus VPN server keep in mind that your computer must trust the
CA that issued the certificate for the VPN server and vice versa for the
connection to succeed. I don't know of any way for Windows to do what Cisco
can do to answer that question for a Windows VPN client. --- Steve
"Robin" <robin.hartley@alcatel.co.nz> wrote in message
news:1117162095.965444.204730@f14g2000cwb.googlegroups.com...
> Hi Steven,
> The issue is with road warrior IPSec per RFC 3193 which is what the XP
> client uses. This is where the L2TP comes in.
>
> It is common to use this for VPN access over public WiFi hotspots which
> don't run any sort of protection, not even WEP. So I used this as an
> example of why I want to protect against a "man in the middle" attack.
>
> Regards,
> Robin
>
- Next message: Robin: "Re: XP client & Server authentication"
- Previous message: Robin: "Re: XP client & Server authentication"
- In reply to: Robin: "Re: XP client & Server authentication"
- Next in thread: Robin: "Re: XP client & Server authentication"
- Reply: Robin: "Re: XP client & Server authentication"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]