-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 05/07/11 09:34, Markus Kötter wrote: > Hi, [...snip...] > > I had a look on the diff for 2.2-beta3 to 2.2.0 and saw no suspicious > changes - maybe because I just don't know how one would suppress the > extensions from being accessible in the certificate. > > So for now I have to use 2.2-beta3. > > Suggestions?
Can you please use git bisect to locate the offending commit? $ git bisect start v2.2.0 v2.2-beta3 then you build and try to run your test routine. If this worked, then you do: $ git bisect good Or if it failed, then you do: $ git bisect bad Do this good/bad thing until git have located the commit which changes the behaviour. You will get a result similar to what you see here: <https://community.openvpn.net/openvpn/ticket/108#comment:1> kind regards, David Sommerseth -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEYEARECAAYFAk4TDoUACgkQDC186MBRfrqczgCfTnHHJTyFgHWwqhrG7+9DcDVQ uWwAn2zUHMQSrwnIvT+fgXpzaEveuppk =7juI -----END PGP SIGNATURE-----
