Scott/Chris,

Apologies for the delay. Took me a bit to figure out the directory structures and scripts such for the developer ISO. Still not sure I understand it very well. :-)

I have built openvpn using the source on the developer ISO. First I built everything using scripts in /home/pfsense/tools/ builder_script. Then, I went to /home/pfsense/tools/pfPorts/ openvpn. I removed the openvpn executable so that I could explicitly force a build with -static--however it's unclear to me if this step was necessary, I was just trying to figure the build system out.

I can confirm that a build from the openvpn/crypto source code in the current pfSense developer system produces a correctly functioning version of openvpn. All tests, including the specific test for the padlock problem in OpenSSL, pass.

Some additional notes:

* The patch I referred to is actually in the pfSense repo: /home/ pfsense/tools/patches/misc/eng_padlock.c.diff.

* The patch has already been applied to openssl in /usr/src/crypto/ openssl/crypto/engine/eng_padlock.c.

* The modification on the openvpn executable in the shipping 1.2 RC2 is April 5, 2006. This predates the first 1.2 release by about a year.

So, It appears that the problem is simply a case of the current openvpn executable not being built/shipped. Should be easy to correct this.

Do I need to file a new bug report, or is the existing one sufficient?

Denny



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to