|
|
Den torsdag 2.mar kl. 12:55 skrev Per-Olov Sjöholm: Hi I would have said yes there is such a version, but i can not seem to find it right now. However, you might possibly do something using the --client-connect scripts if the version is even reported as a variable. It does NOT appear like it is that in those old outputs i have from running a --client-connect script. I think it was "--disable-occ Don't output a warning message if option inconsistencies are detected between peers. An example of an option inconsistency would be where one peer uses --dev tun while the other peer uses --dev tap. Use of this option is discouraged, but is provided as a temporary fix in situations where a recent version of OpenVPN must connect to an old version. " that made me think that there was an option. (the above is taken from manpage for beta 2.1 series) However, dont worry, i have a suggestion that i think will work very well. Simply revoke the certificate and sent them a new VPN package complete with a new openvpn version.
------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! Openvpn-users mailing list Openvpn-users@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/openvpn-users |