Re: [Openvpn-devel] Paid Engagement

Hi, On 09-10-14 18:17, Arne Schwabe wrote: >> So, it looks like running rsa_sign with a cert/key pair coming out of >> the cryptostore store is causing some low level openssl problems. >> Don't know how easy it is fix, but most likely it's not inside the >> OpenVPN code... >> > Pretty easy (for

Re: [Openvpn-devel] Paid Engagement

> > So, it looks like running rsa_sign with a cert/key pair coming out of > the cryptostore store is causing some low level openssl problems. > Don't know how easy it is fix, but most likely it's not inside the > OpenVPN code... > Pretty easy (for OpenSSL standards...). You have to use the

Re: [Openvpn-devel] Paid Engagement

Am 07.10.14 16:32, schrieb Sio Poh Tan: > Hi Samuli, > > Thanks for your reply. I've checked on the link that you provided. However, it does not mention whether the Windows Crypto API integration supports TLS 1.2 implementation. I understand that it does support TLS 1.0 implementation, similar to

Re: [Openvpn-devel] Paid Engagement

Hi Samuli, Thanks for your reply. I've checked on the link that you provided. However, it does not mention whether the Windows Crypto API integration supports TLS 1.2 implementation. I understand that it does support TLS 1.0 implementation, similar to the OpenVPN community version. If the OpenVPN

Re: [Openvpn-devel] Paid Engagement

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Have you checked if the OpenVPN Connect client (bundled with the Access Server) meets your requirements? See section 5 in here: - -- Samuli Seppänen Community Manager OpenVPN

[Openvpn-devel] Paid Engagement

Hello OpenVPN Developers, I understand that the current version of OpenVPN supports implementation of TLS 1.2 using exported cert and key. However, I have a project that requires implementation of TLS 1.2 using cryptoapicert. If any developer is interested to work on this implementation in