|
|
Hi Ralf, I've run out of options here... there seems to be nothing wrong with the p12 file. All I can think of is a openssl library conflict on the client machine, e.g. there's another version of ssleay32.dll installed on the client box. A re-install of openvpn might alleviate that problem but as you stated, you don't own the box. I am curious what the 'openssl pkcs12' commands would show on the client's machine instead of on your (correctly functioning) PC. cheers, JJK Ralf Hildebrandt wrote: > * Jan Just Keijser <janjust@xxxxxxxxx>: > >> Hi Ralf, >> >> OK, so your pkcs12 file contains a cert and a priv key that belong >> together; the p12 file seems to contain 2 certs, is that correct? can >> you try creating a new pkcs12 with only the correct cert+priv key pair >> in it? >> > > Sorry, this p12 works just fine on my own installation > > >> It should not matter, as far as I understand the PKCS12 format but I >> just want to make sure that Windows is not choking on the 2 certs in a >> single pkcs12 file. >> >> Also, sad but true: have you tried re-installing openvpn on this box? >> > > It's not my box. > > ____________________________________________ Openvpn-users mailing list Openvpn-users@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/openvpn-users |