Message-ID: <459CD3BD.4010506@...334...> Date: Thu, 04 Jan 2007 12:15:25 +0200 From: Faidon Liambotis MIME-Version: 1.0 References: <20070103073706.GA11588@...997...> <9e0cf0bf0701031135ye497473tf9b18cc2037fbca5@...278...> In-Reply-To: <9e0cf0bf0701031135ye497473tf9b18cc2037fbca5@...278...> Subject: Re: [Openvpn-devel] [PATCH v2] Use CryptoAPI to verify certificates List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit To: Alon Bar-Lev Cc: openvpn-devel@lists.sourceforge.net Hi, Thank you for your comments. Alon Bar-Lev wrote: > On 1/3/07, Faidon Liambotis wrote: >> Ok, here's another try, even though I didn't get any comments on the >> first one :-) >> >> This is a totally different approach; the previous one was flawed in at >> least two aspects: > > This is better. > But you should use CertVerifyCertificateChainPolicy in order to verify > chain, you should have two policies, one for server and one for > client... I've thought about it but didn't implement it because the only policy I could think of was the nsCertType checking which is already being done by OpenSSL if the user requested it. > I think you can remove the global variable you added to ssl.c and put > it in the session. True, I will fix this. Regards, Faidon