|
|||||||||||
|
Re: [Users] Super-freeswan and Windows 2000, using certs X.509 - 'Negotating IP Security' while pinging
From: Mark Le Noury <markl(at)bbd.co.za>
Date: Tue Sep 30 2003 - 05:16:07 EDT
I had a similar problem and was able to fix it by manually specifying the CA certificate using the IP security policies MMC snap in on the W2K cliet. For some reason I could never get Marcus Mullers' tool to correctly "guess" the right one using the syntax that Nate Carlson describes. Nate Carlson says that you should use : rightca="C=US,S=State,L=City,O=ExampleCo,CN=CA,Email=host@example.com" in the clients ipsec.conf. What I did was run Marcus' tool once so that it created the FreeSwan policy, then edit it and change the CA cert to the correct one manually. You will also need to manually assign and un-assign it using the MMC snap in to turn the rule on and off (because every time you run Marcus' tool it deletes and re-creates the FreeSwan policy). Thanks, Mark -----Original Message-----
Hi everyone!
I'm rather newbie to freeswan/ipsec thing and would like to know where
is a problem in the such case:
freeswan patch
I'm using roadwarrior-net connection. Everything seems to work so far
that I launch ipsec.exe
error messages).
Suggestions - where to look at, what to check, etc.
Thanks in advance :),
FreeS/WAN Users mailing list users@lists.freeswan.org https://mj2.freeswan.org/cgi-bin/mj_wwwusr FreeS/WAN Users mailing list users@lists.freeswan.org https://mj2.freeswan.org/cgi-bin/mj_wwwusr Received on Tue Sep 30 06:29:33 2003 This archive was generated by hypermail 2.1.8 : Wed Aug 23 2006 - 13:01:34 EDT |
||||||||||
|
|||||||||||